Jesús Cea Avión <j...@jcea.es> added the comment:

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.

----------
nosy: +jcea
resolution:  -> invalid
status: open -> closed

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue14041>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to