[sqlite] 2.8 LOCK problem

[Michael Keilhofer]

Earlier I reported I was having trouble executing a statement while in a 
loop that performed a non-callback read of some records. Ulrik P. was 
nice enough to suggest opening a whole new connection.

But I find that even though I do another sqlite_open() all I did was 
change my error from SQLITE_LOCKED to SQLITE_BUSY.

Why would sqlite think the database is busy when I've never performed a 
single insert/update/delete? i.e., I've only performed SELECT statements 
and want to perform an UPDATE.

Is there any way to identify what sqlite is doing that it thinks it 
needs an exclusive lock?

Thanks,
Michael