On 26 Nov 2011, at 2:15pm, Pavel Ivanov wrote: > On Sat, Nov 26, 2011 at 9:03 AM, Simon Slavin <slav...@bigfraud.org> wrote: >> On 26 Nov 2011, at 2:00pm, Pavel Ivanov wrote: >> >>> When sqlite3_step returned SQLITE_BUSY you have to call sqlite3_reset >>> before calling sqlite3_step again. >> >> If your statement is a SELECT returning 50 rows, and you've already read 20 >> of them by the time you get the _BUSY, do you get the first 20 again after >> doing the _reset ? > > This is impossible. On any SELECT statement you either get SQLITE_BUSY > before the first row or you don't get it at all.
Ah, so it's the first _step which does the locking, rather than the _prepare. Okay, that makes the programming easier than if you might have to reset at any _step. Thanks. Also to J-C. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
