Timeline for Should one use a separate database for application data and user data?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 21, 2012 at 14:06 | comment | added | Jon Raynor | I think the single database is fine with the update scripts. One case to make for a new file is if the update is massive, say 1 million inserts, then its easier to just lay down a new file. If you updates are not that massive, update scripts will work fine. | |
| Mar 21, 2012 at 0:50 | comment | added | trycatch | @JonRaynor Well, the tables are already separated, so the boundary already exists, it's just a matter of patch-ability. I'd have to update via a script that does a bunch of inserts, rather than be able to just copy over an updated database file. | |
| Mar 20, 2012 at 17:15 | comment | added | Jon Raynor | Just use different schemas, Application.Table.Column vs. User.Table.Column . One database, two schemas, then you have defined boundary between application and user data. | |
| Mar 20, 2012 at 3:57 | history | answered | GrandmasterB | CC BY-SA 3.0 |