You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Currently, all tables of each module are created within the default PostgreSQL schema "public". In order to improve and ease the identification of the tables, the usage of different schemas (one for each module) was targeted.
After some investigations, it became clear that while this approach works, it has three significant drawbacks.
We were not able to automate the creation of different schemas at database creation time.
Instead of easing the work to look for specific tables, it got even worse because you would need to know in advance to which module the desired table belongs.
For some tables, determining the module is not easy (or even "impossible").
Conclusion
As before, we will not use different schemes in the database.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Description
Currently, all tables of each module are created within the default PostgreSQL schema "public". In order to improve and ease the identification of the tables, the usage of different schemas (one for each module) was targeted.
After some investigations, it became clear that while this approach works, it has three significant drawbacks.
Conclusion
As before, we will not use different schemes in the database.
Beta Was this translation helpful? Give feedback.
All reactions