[CentralOH] Read-Only Database

Austin Godber godber at gmail.com
Tue Nov 9 23:42:49 CET 2010

Really, was your data actually highly structured or were you trying to use
it simply as a key value store?

I would be tempted to try this:

Or yeah, if dbm covers it, I would stick with that.  The simplest possible
solution.  Good recommendation Catherine (congrats on your change of
situation too).


On Tue, Nov 9, 2010 at 4:20 PM, Catherine Devlin <catherine.devlin at gmail.com
> wrote:

> On Tue, Nov 9, 2010 at 3:53 PM, Mark Erbaugh <mark at microenh.com> wrote:
>> But you're right about SQLite. That's a good general purpose choice and
>> probably sufficient. I read somewhere that trying to find the "best" Python
>> module for a given application can drive you crazy.
>> I've actually had cruddy performance from SQLite on large databases.  It's
> optimized for ease of use, not speed.
> The Lore says that nothing-but-nothing beats simple key:value storage like
> dbm for raw speed - no RDBMS, no oh-so-trendy NoSQL database, nothing - and
> it sounds like your application would qualify.  Have you tried your speed
> with dbm?  800k rows sounds like something it would handle easily.  I've
> never heard of optimizing it for read-only but I bet you won't need to.
> --
> - Catherine
> http://catherinedevlin.blogspot.com
> _______________________________________________
> CentralOH mailing list
> CentralOH at python.org
> http://mail.python.org/mailman/listinfo/centraloh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/mailman/private/centraloh/attachments/20101109/e5c35f1d/attachment-0001.html>

More information about the CentralOH mailing list