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 jcea
Recipients jcea, totycro
Date 2012-02-17.16:09:43
SpamBayes Score 3.5402893e-05
Marked as misclassified No
Message-id <1329494984.96.0.660180951941.issue14041@psf.upfronthosting.co.za>
In-reply-to
Content
The file is corrupted:

"""
jcea@ubuntu:/tmp/z$ /usr/local/BerkeleyDB.5.3/bin/db_verify data.db 
db_verify: BDB0551 Page 0: nonsensical free list pgno 55
db_verify: BDB1107 Page 2: offpage item 19 has bad pgno 70
db_verify: BDB1107 Page 20: offpage item 5 has bad pgno 59
db_verify: BDB1107 Page 36: offpage item 9 has bad pgno 94
db_verify: BDB1107 Page 37: offpage item 9 has bad pgno 57
db_verify: data.db: BDB0090 DB_VERIFY_BAD: Database verification failed
BDB5105 Verification of data.db failed.
"""

For "real world" usage, you must use Berkeley DB transactional storage mode. If you use a concurrent datastore or anything like that (anything more "simple" that the transactional mode), you can corrupt your database if the application or the computer crash in a bad moment. Or if you try to backup the database while writes are in progress, for instance. Briefly: use the transactional mode and read the Oracle documentation carefully!.

Closing the report as invalid, since the database is actually corrupt.
History
Date User Action Args
2012-02-17 16:09:45jceasetrecipients: + jcea, totycro
2012-02-17 16:09:44jceasetmessageid: <1329494984.96.0.660180951941.issue14041@psf.upfronthosting.co.za>
2012-02-17 16:09:44jcealinkissue14041 messages
2012-02-17 16:09:43jceacreate