On 29/06/2012 9:52 PM, Simon Slavin wrote:
When you're deleting the database file, look for any other files in the same folder with
names that start with "mydbname" and anything after that, including any
extension. (Marcus's theory) Tell us what they're called.
Make sure you're quitting the shell tool with '.quit', not just CTRL-C ing out
of it.
First try the above two. If they don't explain what's wrong,
Using the shell tool, delete one of the rows which has magically appeared. Or even
the whole table. Make another row or table with different data in. Then repeat
the quit & delete procedure.
When you go back into the shell tool, do you get the same old bad data or the
new bad data ?
Simon.
Yes, of course all files are removed, as far as the "dir" command is
concerned (with hidden files/folders shown). And yes, I'm using ".quit".
I've tried deleting that row, but the stuffed up DB contains a trigger
that I have long removed from my code, which prevents that (because it
relies on something that has also been long removed from the db's
structure). So, I've inserted a new row using the shell tool, then
".quit", deleted all files, ran my app, which created a supposedly empty
database (stepping through the code). After that quit my app, open the
DB using the shell and my new row was there - eventhough it contains
impossible data, which would have never been entered using the app
(proving that the app is not inserting data on its own). So, it's the
new bad data :)
Dennis
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
