Hello, recently some of my customers suffered from data corruption in sqlite database. Hopefully, no data(?) was lost. The person, that found this bug, doesn't recall what was doing that time; there's a hard machine lock-up possible (on Win98, I'd hardly connect this with sqlite itself).
Anyway, the database contained one corrupted row, which had same value in "unique" field as some other record. After .dump / restore (and loosage of that one, corrupted row) database seems to be fine. Opening and reading from that damaged table resulted in coredumps (unix) and creashes (win32). I have the damaged file. How can I debug, what was wrong - and if it really was sqlite fault? Sqlite was used via py-sqlite 0.5 wrapper on win32. Regards, -- Michal Pasternak :: http://pasternak.w.lub.pl :: http://winsrc.sf.net "There's so much comedy on television. Does that cause comedy in the streets?" -- Dick Cavett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
