How to properly design a database for notifications?

Question

MySQL

Hello everyone, how to correctly implement a table or tables for the notification system?
For example:
We have the following table of notifications (simplified):
1. user
2. type (table name in the database)
3. id_type (id in this table)
Notifications can be of a completely different plan, and information needs to be obtained to form them from different tables, like do it right? Not to do a pack of requests to different tables? The idea with left outer join also seems strange, in general I can’t figure out how best to store and then conveniently display?
Tell me exactly according to the logic of the whole chain, thank you in advance)

Answer 1

If these are notifications of the "sent and forgotten" type, then, IMHO, generate notifications and store ready-made ones. For people in text form, for programs / services - in JSON / XML / serialization.