This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ghaering
Recipients ghaering, gregburd, gregory.p.smith, jcea, josiahcarlson, pitrou, rhettinger, skip.montanaro
Date 2008-09-11.10:37:45
SpamBayes Score 5.28686e-07
Marked as misclassified No
Message-id <1221129494.72.0.298685110284.issue3783@psf.upfronthosting.co.za>
In-reply-to
Content
I like Skip's version better, because it's closer to the dbm
"specification" instead of trying to mimic bsddb (first, last, etc.).
I'd like to keep such things out.

I've made a few changes to the sandbox project which I will check in
later today. The most important change is support for a "fast mode",
which doesn't commit changes until you call the synch() method. synch()
is also called on close().

Perhaps we should do automatic commits every n (like 1000) changes, too?

What's all this ORDER BY in both your implementations about? The dbm
"spec" says nothing about keys being ordered AFAIC. Can we get rid of these?
History
Date User Action Args
2008-09-11 10:38:14ghaeringsetrecipients: + ghaering, skip.montanaro, rhettinger, gregory.p.smith, jcea, josiahcarlson, pitrou, gregburd
2008-09-11 10:38:14ghaeringsetmessageid: <1221129494.72.0.298685110284.issue3783@psf.upfronthosting.co.za>
2008-09-11 10:37:45ghaeringlinkissue3783 messages
2008-09-11 10:37:45ghaeringcreate