Clemens Ladisch <clemens at ladisch.de> wrote: > > https://www.sqlite.org/lang_select.html talks about LIMIT & OFFSET, > > without mentioning that is a bad idea. >> Neither does it mention that it is a good idea. >> > can I do that or not (will it become sluggish if I do that) ? >> When you use large OFFSET values, the database must compute all these > rows before throwing them away.
Can anyone describe a situation for which this style of LIMIT & OFFSET is advisable from the application's point of view? (The DBMS costs are obvious enough.) For me this is the easiest way to implement a scrolling cursor. Otherwise I will have to record for each table the condition I use to scroll it. So if there is an easier way to implement the scrolling cursor please let me know. Thanks! Qiulang At 2016-03-02 21:02:27, "??" <qiulang2000 at 126.com> wrote: Here(http://www.sqlite.org/cvstrac/wiki?p=ScrollingCursor) said "Do not try to implement a scrolling window using LIMIT and OFFSET. Doing so will become sluggish as the user scrolls down toward the bottom of the list.?. But the page also said "This information is obsolete? https://www.sqlite.org/lang_select.html talks about LIMIT & OFFSET, without mentioning that is a bad idea. So my question is can I do that or not (will it become sluggish if I do that) ? Thanks Qiulang
