in web2py you can do db().select(limitby=(a,b)) and this translates in fetching (b-a) records starting with the a-th. On postgresql this is implemented as LIMIT (b-a) SKIP a.
Oracle does not support LIMIT and does not support SKIP/OFFSET therefore this is implemented using three nested selects as suggested by the official oracle documentation (btw Django does it with 2 nested selects and that is not the oracle recommended way). In practice web2py effectively implements pagination on Oracle except that our technique breaks with some joins. MSSQL supports LIMIT but not SKIP/OFFSET. We have not found a way around to we actually fetch b records and then we discard the first a records at the web2py level. This is not a satisfactory solution if there are many records. Massimo On Jan 5, 1:13 am, "K.R.Arun" <[email protected]> wrote: > On Jan 5, 1:26 am, Thadeus Burgess <[email protected]> wrote: > > > You say that MSSQL and Oracle do not support pagination? In what ways does > > the database support pagination? How would you take advantage of this for > > say PostgreSQL on the database level instead of the query level? > > > -Thadeus > > I too loves to here about it. > > Arun -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
