At 05:33 AM 12/23/2004, you wrote:
Inserting binary data without encoding it should *not* corrupt the
database. It might make it difficult to get your data back, but
other records in the database should be uneffected and the kinds
of errors you were seeing from PRAGMA INTEGRITY_CHECK should not
Michael Hunley wrote:
At 03:43 PM 12/22/2004, you wrote:
See section 6.0 in http://www.sqlite.org/lockingv3.html.
That article is on SQLite version 3, but the methods for
corrupting a database apply equally well to version 2.
Thanks. Unfortunately, none of these seem terribly likely. The user
At 03:43 PM 12/22/2004, you wrote:
See section 6.0 in http://www.sqlite.org/lockingv3.html.
That article is on SQLite version 3, but the methods for
corrupting a database apply equally well to version 2.
Thanks. Unfortunately, none of these seem terribly likely. The user
reported that nothing
Michael Hunley wrote:
What else could cause this "corruption?"
See section 6.0 in http://www.sqlite.org/lockingv3.html.
That article is on SQLite version 3, but the methods for
corrupting a database apply equally well to version 2.
Is there any way to repair the db so the user does not lose his
4 matches
Mail list logo