Andrii Motsok wrote: > "If a SELECT statement that returns more than one row does not have an ORDER > BY clause, the order in which the rows are returned is undefined" > > We have scenario: > * database is opened in WAL mode > * 10 rows have been read to container1 > * database has been checkpointed > * database has been closed > * database has been opened on DELETE mode > * 10 rows have been read to container2 > > Can we assume that container1 == container2 ?
This assumption happens to be true in the current version of SQLite, if no other changes are being made to the database before re-opening it. But to assume this is extremely dangerous, because you don't know how your application will be changed in the future. Just use ORDER BY. Regards, Clemens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
