What about storing the rowid's of the offsets in a separate table and using that?
How dynamic is your data? Michael D. Black Senior Scientist NG Information Systems Advanced Analytics Directorate ________________________________ From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on behalf of Fabian [fabianpi...@gmail.com] Sent: Wednesday, October 12, 2011 8:34 AM To: General Discussion of SQLite Database Subject: EXT :Re: [sqlite] OFFSET Performance 2011/10/12 Igor Tandetnik <itandet...@mvps.org> > > See if this helps: http://www.sqlite.org/cvstrac/wiki?p=ScrollingCursor I tried to implement the method as suggested in the article, but it will only work for pagination where the user is only allowed to go 1 page back or 1 page forward (since you have to remember the last rowid). In my case, the user is allowed to jump to the last page, without visiting any of the previous pages, making the suggested method impossible to implement. _______________________________________________ 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
