On 18 Aug 2011, at 2:03pm, Kristoffer Danielsson wrote: > Hi, The problem is that the database is around 100 MB large (the error goes > away if I remove unimportant data). Also, it contains data I'd like to keep > private. I do have a specific select query that produces what I believe is a > data error (tested in the latest SQLite version).
First run an integrity check on the database: http://www.sqlite.org/pragma.html#pragma_integrity_check Then if that doesn't spot any problems ... Make a copy of the database, then working with the copy, delete data which doesn't matter to your query, leaving just a small database with perhaps one or two rows which demonstrate the problem. If you can do this, you can then run the SQL command 'VACUUM' on the resulting database and this will dramatically reduce the file size. Once you'd done this, test that your demonstration of the problem still works. Then you might think about either anonymising the data so it doesn't contain anything sensitive, or sending the small file to Doctor Hipp with an explanation of the problem. On 18 Aug 2011, at 2:10pm, Kristoffer Danielsson wrote: > http://www.mailinglistarchive.com/html/sqlite-users@sqlite.org/2011-04/msg00315.html Oh. Those two queries could easily return different rows if you have a NULL in the JOINing columns. Any chance of that ? Otherwise, identify which query is returning incorrect data and break it down to see which clause is causing the problem. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
