| From: | Anto Aravinth <anto(dot)aravinth(dot)cse(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Building a notification system. |
| Date: | 2018-07-15 16:58:32 |
| Message-ID: | CANtp6R+t9U79bh0-1MTwMpy0V4jhxEuMNNikvBvRAvpYsRuuew@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
So just maintaining a notification table along with user id would do I
believe. Just notifies the user if he/she has the userid in notification
table and its not in read state.
On Sun, Jul 15, 2018 at 10:23 PM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Sunday, July 15, 2018, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
> wrote:
>
>> On Sunday, July 15, 2018, Anto Aravinth <anto(dot)aravinth(dot)cse(at)gmail(dot)com>
>> wrote:
>>>
>>> I'm not sure, how to get started with this. Read about NOTIFY:
>>> https://www.postgresql.org/docs/current/static/sql-notify.html
>>>
>>>
>>> Not sure that fits my use case, thanks for your help in this.
>>>
>>
>> It doesn't. You need to record time stamps for the relevant events and
>> use them to decide what is new and what is old.
>>
>
> Or, to avoid time skew issues, an equivalent protocol using serial
> (big)integers (see create sequence)
>
> David J.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Igrishin | 2018-07-15 16:59:08 | Do we need yet another IDE (SQL development assistant) for PostgreSQL? |
| Previous Message | David G. Johnston | 2018-07-15 16:53:45 | Re: Building a notification system. |