Stefan Sperling <s...@elego.de> writes: > If you run this version of your test, it will run in an endless loop. > The callback inserts new values, the caller will see those and invoke > the callback again.
Hmm, I expected the select to block the write causing it to return SQLITE_BUSY. That is what happens if the write is done by a separate process, but apparently not when it's the same process (or maybe it's using the same database handle that makes it work). -- Philip
