OK, this seems like a simple thing, but I'm stuck and looking for
inspiration or clues.
How can sqlite3_prepare_v2() return SQLITE_BUSY for a simple SELECT
statement when in WAL mode?
Immediately prior, a sqlite3_exec("BEGIN TRANSACTION") succeeded.
The failing call is just sqlite3_prepare_v2(), and the SQL passed is
nothing more than
SELECT (explicit column list) FROM (table) WHERE (pk) = @Id
So if WAL mode means writers don't block readers, it seems like preparing a
SELECT statement should not give me error code 5. Ever?
Am I missing something?
Thanks,
--
E
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
