Database Support for forms and various registrations #455
Replies: 3 comments 3 replies
-
@Pruthaa17 Here's a discussion for this. You can go ahead here as per #449 (comment) Once we finalise this, we can create issue from discussion and will assign you |
Beta Was this translation helpful? Give feedback.
-
@Pruthaa17 I think your next step could be to find out the tables and schema needed for our project. They can make it easier to implement them without any confusion or further modifications. For this, you can use https://drawsql.app/ or https://www.eraser.io/use-case/data-model For reference the following I did while I was preparing for the GSOC proposal: Tip Specify the 1-1 and 1- many relationships between tables too |
Beta Was this translation helpful? Give feedback.
-
https://drawsql.app/teams/rapidoc/diagrams/db101 , Can you please review it and suggest some changes ? @varshith257 |
Beta Was this translation helpful? Give feedback.
-
PostgreSQL is one I prefer as I worked with three of these dbs. But I can't say we use this only for our project as every usecase has other preferences over dbs in projects. Submit a report of your findings, why we prefer PostgreSQL for our project, and why not MongoDB and MySQL. Pros and cons of them and what you are suggesting to use finally based on your research?
Beta Was this translation helpful? Give feedback.
All reactions