Timeline for Logical separation of database content
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 20, 2018 at 16:23 | comment | added | Danielku15 | Accepted this answer as it describes both common approaches. It seems there are no out-of-the-box solutions and you either need to go for schema changes with IDs or you go for a separate database per tenant. | |
| Aug 20, 2018 at 16:22 | vote | accept | Danielku15 | ||
| Aug 6, 2018 at 21:31 | comment | added | Lewis Pringle | No disagreement, but he didn't ask how to re-organize the entire database, just to solve a specific problem. But if his time budget permits, that makes sense. Though - note - it probably has impact on his entire code base because of the ORM layer (unless he writes custom mappers). @GregBurghardt | |
| Aug 6, 2018 at 20:32 | comment | added | Greg Burghardt | Putting a "blog Id" on multiple tables that aren't directly linked to a blog will still be a maintenance headache. Normalize this first. You can always create database views to flatten out the tables to make querying easier. Views and proper indexes will take you a long way, and then denormalize the database only to solve specific performance issues. | |
| Aug 6, 2018 at 20:16 | history | answered | Lewis Pringle | CC BY-SA 4.0 |