Data model
Opened this issue · 2 comments
#9
I suggest to split out this topic not to confuse participants and to make the discussion more productive.
Here is the link to the actual scheme (which is currently the initial draft): Data Model
And a small description of the tables:
user - user instances
user_profile - user's additional information and probably settings
user_authentication - authentications track
subscription - the types of subscriptions an author creates for his subscribers
user_subscriptions - M2M containing each user's subscriptions and their validity
mailing - mailing instances an author creates
mailing_subscriptions - M2M containing types of subscriptions the mailing is sent to
post - author posts
post_subscriptions - M2M containing types of subscriptions the post is visible to
post_likes - post likes track
donation - a dedicated donation initiated by tan author
transaction - payments track
payable - intermediate for payable instances
I intentionally did not populate the models with the complete sets of fields to avoid visual overload.
If someone needs a detailed description, let me know )
Please comment
@igorek097 hi!
I propose use mermaid to draw DB schemas. Mermaid is markdown extension, supported by GitHub now. Example of Entity Relationship Diagram schema in mermaid in live editor. Propose to create new markdown file in the /docs folder in repo for this schema:)
https://dbdiagram.io/d/623d7cedbed6183873f8c57f
Updated in accordance with the recent conf. minutes and a new proposed user model