Timeline for Why use a database instead of just saving your data to disk?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 9, 2020 at 23:03 | comment | added | Lie Ryan | @EamonNerbonne Perhaps better phrased, with an RDBMS, you can ignore how stuff is represented until it actually shows up as a real world problem. Only when things becomes a problem, then you can analyse the issue and in most cases the solution would be in the form of just add a few well placed index, and the RDBMS' query planner will take care of taking advantage of that index on all other operations that might benefit from it, and updating it. OTOH, if you're writing your own data storage using filesystem, you'll have to update the rest of the application. | |
| May 19, 2013 at 7:42 | comment | added | Eamon Nerbonne | I'm a little leery about the idea that you can just ignore how stuff is represented. While you can ignore this, if you do, and esp. if you do write a slightly more complex query, it's exceedingly likely your application can no longer scale. "Adding an index" is not always possible - you've got writes to contend with, and it simply doesn't help that much with queries whose complexity spans multiple tables. When indexes are necessary that implies you've lost the benefit of interactive queryability since only specifically structured queries are answerable in reasonable time. | |
| Mar 14, 2013 at 14:12 | history | answered | Emperor Orionii | CC BY-SA 3.0 |