That is precisely what I am doing. The client just sends a ‘seen’ message to the notification channels (I have multiple for different notification types) to indicate that it has seen up to ‘now’.

Would you mind elaborating on how you structured your notification relationships?

I’m trying to accomplish something similar, Multiple Polymorphic Associations in Ecto, and would be curious how you tracked your model changes in the db.

Thanks!

In what way? The notifications via broadcasting? The database itself? The helpers that tie them together?

Hi there!

I was predominantly meaning in the database itself and/or the helpers.

My biggest challenge was:
How do you structure your tables to track the model changes?

1. A separate notification table for each model) ie model_a_notifications, model_b_notifications.
2. A many-to-many association with a generalized notification?

Thanks

I just did it very simple, a table of just ‘topics’, ‘users’, and 'datetime’s as I recall (do not have it in front of me at moment).

For the notifications case, you can also put all the relevant information in a map, including the user_id, post_id and everything else you may want to show the user. When doing a notification system, it is often best to have all the data you need in a single lookup instead of traversing multiple tables after the information you want. However, do include the source data in case you need to reconstruct the notifications later on.

Thanks for the advice José!

Good idea. That will simplify the approach In was taking. Thanks

That’s what I do via a PostgreSQL JSONB (Ecto :map) type for my generic notification store.