Nothing obvious springs to mind but I do see that you are not checking the
values returned by most of your sqlite_exec() calls. Perhaps you could write a
little routine that does the sqlite_exec() and then asserts that the value
returned is SQLITE_OK. It may be that it's actually one of the other calls
which is getting the first indication of error.
Apart from that, and the fact that you don't need the semicolons everywhere, I
don't see anything bad about your code.
Thanks for your reply. The example I wrote is just an example what the
code does and the output from when the threads try to access the
database and when the error occur (I've wrapped the database access in
c++ try/catch in the real app). Is it possible to find out the reason
for the lock some way? Any internal debug I can enable to help me figure
out what's going on?
What I'll do now is to strip down my large application more and more
until I hopefully find the cause of the problem, but I'm interested in
knowing about good ways to debug sqlite processing anyway.
Best regards,
Daniel
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
