DRH, I guess, the question being asked is twofold. Should there be an error returned at all ? Or if there is an error, wouldn't SQLITE_BUSY be more appropriate... So the users app could attempt a retry?
Since there is an error, it seems that the error message is not the same as the return code from the Step command. Thanks, Ken sqlite-users@sqlite.org wrote: sqlite-users@sqlite.org wrote: > Hi all, > > Hopefully you can help, while running sqlite version 3.5.5 > > Two seperate threads each attempt to run a vacuum command against the same > db. Each thread has an independent connnection to the db. > > One thread succeeds and the other gets a return code of 1 (SQLITE_ERROR) from > sqlite3_step. > > The sqlite3_error msg generated is "SQL logic error or missing database". The > Vacuum command is executed using the sqlite3_prepare_v2 interface. > > This only seems to occur when the database is actually vacuumed by the first > thread. The second thread then gets this error. > > Thanks for any help. Are you concerned that you are unable to do two vacuums simulataneously, or are you asking that the error message returned be adjusted to be more lucid? -- D. Richard Hipp _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
