> >>The only thing that can bite you is if >>you are in process of fetching rows from some select statement and you >>update row that was just fetched or update/insert rows that would have >>been fetched later by the select statement. > > As I understand it, simply wrapping every batch operation (Read, Write > or Read_Modify_Write) inside an IMMEDIATE transaction is all that's > needed to prevent such bad things from happening, or am I misguided?
It doesn't matter if you are in a transaction or not, changing rows while inside a fetch loop on the same table may lead to problems. DRH gave a nice explanation about this issue: http://www.mail-archive.com/sqlite-users@sqlite.org/msg44025.html Marcus > > _______________________________________________ > 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
