>> Do you mean you're making changes as you call SQLite to _step() through the >> results of the SELECT ? Or do you read all the results of the SELECT into >> memory, then make changes to the database ? > > The former.
Oh, I completely forgot that people can do that. So, Robert, you case is exactly the case I was talking about. As Simon said your SELECT opens read-only transaction and then as you issue your first UPDATE this transaction have to be converted to writing one. This is a call for problems. So you better to issue "BEGIN IMMEDIATE" before you execute your SELECT statement. BTW, I hope you don't change the table you selected in this scenario? Pavel On Mon, Jun 14, 2010 at 10:43 AM, Robert Latest <boblat...@googlemail.com> wrote: > On Mon, Jun 14, 2010 at 4:36 PM, Simon Slavin <slav...@bigfraud.org> wrote: > >> Do you mean you're making changes as you call SQLite to _step() through the >> results of the SELECT ? Or do you read all the results of the SELECT into >> memory, then make changes to the database ? > > The former. > robert > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
