The thing is that my system sometimes produces malformed database, but I don't know what cause that. I'm trying to collect possible cases when database gets malformed. I'm going in this direction because it is not possible to debug system to reproduce condition. Because of that question is: can lack of journal file produce malformed database file?
Greetings, Darko F. Igor Tandetnik wrote: > Darko Filipovic > <[EMAIL PROTECTED]> wrote: > >> I've tried...(not with UFO :D ). Nothing happens, database is not >> corrupted and that is what confuses me...I thought it should not be >> readable (malformed) ?! >> > > Not necessarily. Suppose you issued an update statement that was > supposed to update 100 records. Before the process crashed, 50 of them > were successfully updated (e.g. they just happened to sit on the same > page), but the other 50 were not. The database is not physically > corrupted - the table and record structure is intact. But it's logically > corrupted, in that some database invariants important to your > application may have been violated. > > Igor Tandetnik > > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > __________ NOD32 3154 (20080603) Information __________ > > This message was checked by NOD32 antivirus system. > http://www.eset.com > > > > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
