On Sep 13, 2012, at 9:30 PM, Igor Tandetnik <itandet...@mvps.org> wrote:
> If records are added by the same transaction that runs the SELECT statements, > then they may or may not be observed (imagine for example that the statement > has an ORDER BY clause, and a new row is inserted that comes before the row > that the statement is currently positioned at). Hmmmm… doesn't SQLite provide read consistency by default (i.e. isolation level SERIALIZABLE [1])? In other words, a select should only ever see what existed at the beginning of the query, and that is that. Or perhaps are you talking about 'dirty reads', aka 'read uncommitted' [2]? Or something else altogether? [1] http://en.wikipedia.org/wiki/Isolation_(database_systems)#Serializable [2] http://www.sqlite.org/pragma.html#pragma_read_uncommitted _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
