Timeline for Logical separation of database content
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 30, 2019 at 10:47 | comment | added | Simon Bergot | This approach can have drawbacks. It leaves room for mistakenly mixing your client's data. Depending on the size of your company and the number of developpers, this can be an unacceptable possibility. If each blog is big, splitting per bd can also facilitate maintenance such as backup management. Splitting per db also allows you to split your db server easily if you are lucky enough to scale. | |
| Aug 7, 2018 at 15:26 | comment | added | Tim Meyer | +1 This should be the way to go. I work in a project where - in the terms of the example in the question - every single table has a "blog_id" column and I cannot recommend it at all. While it might look like a convenient approach at first, it is actually less work to just filter any table by its parent key, which must usually be done anyway. Other than that, I recommend the Boyce Codd Normal Form (BCNF; en.wikipedia.org/wiki/Database_normalization#Normal_forms) | |
| Aug 6, 2018 at 12:24 | history | answered | Misamoto | CC BY-SA 4.0 |