I take that back, this does not solve it, since web2py ends up
reversing the query, so the next 100 rows is actually the next 100
from the end.
-Thadeus
On Wed, Dec 30, 2009 at 11:58 PM, Thadeus Burgess <thade...@thadeusb.com> wrote:
> What I'm trying to do:
>
> Sort by a row (say last_name). Then view the next 100 rows.
>
> What I expect:
>
> For the next 100 to continue with the sorted query
>
> What happens:
>
> The query resets
>
> How to fix it:
>
> I'm sure there is a better way, but the orderby get_vars is being lost
> in the middle... so
>
> <h3>{{=nrows}} {{=T("selected")}}</h3>
> {{if start>0:}}[ {{=A(T('previous 100
> rows'),_href=URL(r=request,f='select',args=request.args[0],vars=dict(start=start-100,
> orderby=request.get_vars.orderby)))}} ]{{pass}}
> {{if stop<nrows:}}[ {{=A(T('next 100
> rows'),_href=URL(r=request,f='select',args=request.args[0],vars=dict(start=start+100,
> orderby=request.get_vars.orderby)))}} ]{{pass}}
> {{if rows:}}
>
> Fixes it in my case. I bet there is a deeper reason as to why web2py
> isn't keeping the correct query in session but I don't have time to
> dive further into this at the moment.
>
> -Thadeus
>
--
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To post to this group, send email to web...@googlegroups.com.
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en.
