Timeline for Whats the best way to determine when it is appropriate to use a database?
Current License: CC BY-SA 2.5
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 23, 2011 at 1:55 | comment | added | Javier | another option is SQLite, which is far lighter on both RAM and disk space, and doesn't have any arbitrary limitations. No wonder it's used by all non-MS smartphones and web browsers. | |
| Mar 23, 2011 at 0:53 | comment | added | Orbling | @Kenneth: They make your installation larger and can increase the codebase. But that is much less than installing a whole database server on a client, that is only usually done when the application is distributed and needs a more substantial database. The Berkeley DB is one of the most commonly used. | |
| Mar 23, 2011 at 0:44 | comment | added | Kenneth | Are there downsides to using lightweight db's? | |
| Mar 23, 2011 at 0:43 | comment | added | Kenneth | This sounds like it might be an ideal solution... I really enjoy utilizing db's! lol | |
| Mar 23, 2011 at 0:32 | comment | added | jprete | A very similar example on the Java side is Derby. I think there are others, too. | |
| Mar 23, 2011 at 0:10 | history | answered | Carson63000 | CC BY-SA 2.5 |