Pardon me for being thick. But the end of what? The end of the sqlite file? The end of a table? The end of a select?
I always thought there was no such thing as "a start or an end" as the database is basically air until you request something from it. Even when you have something, it could change in the very next exec of the query. So what is the "start" and what is the "end"? Looking at a sqlite file as a whole, is it the row at the very end of the file or the last row inserted, which could be located in some page that is not even the end of the file. I don't think I understand too well. On Tue, Oct 15, 2019 at 11:53 AM Jens Alfke <j...@mooseyard.com> wrote: > > > > On Oct 15, 2019, at 9:44 AM, Simon Slavin <slav...@bigfraud.org> wrote: > > > > You can then remember the value(s) of some column(s) of the row > returned, and watch for the same one(s) when you do your desired SELECT. > > As long as all the result rows are unique… > > All of these workaround seem more expensive/complex than just adapting > your code so it doesn't have to know the last row in advance. > > —Jens > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
