-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs(back-end): add schema #133
Milestone
Comments
@JeremyFriesenGitHub @JowiAoun Priority to get this merged in |
It's ready for review @HasithDeAlwis |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🆘 What is the problem at hand?
We recently introduced a database for portal, using DrizzleORM. It is time to write the initial schemas previously discussed.
🚀 What is the impact of the problem? How is this problem important? How does it affect users/developpers?
Beginning with writing the database schemas allows us to have a better overview of requirements and lets makes other developers aware with the type of data they are working with.
💀 Additional context
We have discussed the initial database schemas previously in issue #71, and are now implementing them with DrizzleORM.
The text was updated successfully, but these errors were encountered: