This repository has been archived by the owner on Apr 18, 2024. It is now read-only.
Redo database structure #148
pavelskipenes
started this conversation in
General
Replies: 1 comment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Proposal
Current database structure is not relational and issues arises higher in the stack due to bad database design. It makes no sense to solve issues in the stack before core problems are addressed. This is a proposal of a new database design from ground up. When it is implemented we can use frameworks like Laravel to create database abstractions, api and so on instead of writing them from scratch as are being done now.
Does this design look good enough for our use case? Would be better to change it now than later.
Notable changes from current design:
admin
,store
andmembers
from justmembers
andweb
.members
table intomembers
andmembership request
.admin.users
have more personal information. The idea is that users can log in and change their description through a profile menu or something similar.Todo:
Attached design does not fully support ERD patterns like many-to-many and zero-or-many etc... So some relations might not be correct in the diagram.
new_database_structure.pdf
This is database markup language that can be used to generate diagrams like above and sql files for import. You can paste this into dbdiagram.io and interactively view it. Note: it does not work well in Brave browser just in Chrome 😞
Beta Was this translation helpful? Give feedback.
All reactions