UPDATE during SELECT about apsw HOT 3 CLOSED

From rogerbinns on June 08, 2009 11:34:54

The specific example I was thinking of was someone who posted to the SQLite mailing
list who was doing 'select * from example order by rowid' and then for each row
returned was doing an update that actually turned into a replace (thereby allocating
a new rowid) on that row. He essentially got an infinite number of results.

You can see the discussion at http://www.mail-archive.com/[email protected]/msg42660.html In summary there are two important things about SQLite. The first is that it does
not get the next row of results until you ask for them, calculating them on the fly.
The second is that changes/transactions on the same connection are not isolated from
each other.

Status: Accepted
Labels: -Type-Defect Type-Other Component-Docs

from apsw.

From [email protected] on June 08, 2009 12:17:40

I see. Thank you very much for the link, that clarifies things a lot.

from apsw.

From rogerbinns on June 08, 2009 17:58:41

I have updated the doc slightly and pointed to the example link above to help make
this all clearer in r453 .

Status: Verified

from apsw.