Another odd thing is that when I call sqlite3_reset on the prepared statement, it also returns SQLITE_BUSY. Should I only reset the statement when it has been executed successfully?
On Mon, Oct 26, 2009 at 2:40 PM, Chris T <citrus...@gmail.com> wrote: > I'm new to sqlite (and sql in general, actually) and came across > something puzzling. > > I wrote a test program statically linked with the amalgamated sqlite > code. When I run a single instance, everything is fine. When I start > a second instance in the same directory they both deadlock. Every > call to sqlite3_step returns SQLITE_BUSY. > > The source code to my test program is attached. It was written in > Visual Studio, so feel free to remove the reference to windows.h and > change the calls to Sleep( ) if you don't use Windows. > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
