-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
🚀 Feature: Refactor Database management #5195
Comments
We actually did have a dedicated schema for each project in earlier days of the project, but that seemed to cause some issues with the Docker MariaDB image. Some developers reported issues with the DB initialization and this forced us to use root permissions which is not a great practice. We can consider doing something like this in the future and maybe make it optional, we're already planning to work on allowing more integrations around managed databases and advanced projects segmentation features that could help achieve this goal as well. |
If I remember correctly, one of the bigger issues also was that the |
🔖 Feature description
Create a new database per project instead of using a unique database.
🎤 Pitch
Hi guys, first of all, congratulation for all the works ! This is an awesome project !!!
I want to know why you choose a global implementation of database. Maybe I'm wrong but I saw you database architecture like this :
appwrite
database_console.teams
table that refers to all teams created from dashboard_<id_team>_databases
table that refers to all databases for the team<id_team>
_<id_team>_database_<id_db>
table that refers to all collections for the database<id_db>
of the team<id_team>
_<id_team>_database_< id_db>_collection_<id_collection>
table that refers to the collection<id_collection>
for the database<id_db>
of the team<id_team>
It wasn't possible to create a new purely database dedicated per projet ? And see in the mariadb instance a database for each app (or project) keeping the table name used by the developer.
Possible use cases :
Thanks,
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: