@david: I am not corrupting the database myself. Users of my application
have sent in corrupted databases (on very rare occassion).
I do not have permission to send you corrupted database at this time.
I can tell you the following:
This problem starts with v3.18.
It works ok with v3.17
Database 1 integrity check result:
*** in database main ***
On tree page 51 cell 1: invalid page number 302055426
Page 373: btreeInitPage() returns error code 11
Page 501: btreeInitPage() returns error code 11
Page 437: btreeInitPage() returns error code 11
Page 54 is never used
Page 55 is never used
Page 56 is never used
Page 57 is never used
Page 58 is never used
Page 59 is never used
Database 2 integrity check result: (no result)
Error: database disk image is malformed.
Database 3 integrity check:
*** in database main ***
On tree page 65213 cell 2: 9595 of 15116 pages missing from overflow
list starting at 65188
Page 70081 is never used
Page 70082 is never used
Page 70083 is never used
... repeat up to
Page 70179 is never used
Despite these errors, using the .dump command mentioned in first post
fixes the problem wonderfully in all 3 databases, and fails in all 3 in
v3.18
If you have a pressing need for the database I can go to the trouble of
contacting the user about it, but I obtained some a long time ago.
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
