[TurboGears] Re: Opinions on paginate changes

Wed, 13 Sep 2006 06:56:03 -0700

I'm currently using PaginateDataGrid to display sortable/pageable SQLAlchemy result sets (which are just lists by default).  Had to modify paginate.py and paginate_datagrid.kid to get it working.  Not sure if my solution if the "right" way, but it works.  Diffs are attached if anyone cares to look.

A feature I'd like to see added: add a sort_value kw arg to the DataGrid.Column constructor.  There are lots of times where the value I want to sort on for a column and the value I actually want to display for that column are different.

On 9/13/06, Kevin Dangoor <[EMAIL PROTECTED]> wrote:

On Sep 12, 2006, at 3:49 PM, Randall wrote:

>
> I'd like to add some features to TG's pagination and would like some
> feedback.
>
> The first is SQLAlchemy support.  paginate.py uses SQLObject's
> SelectResults to order the result set.  SA has similar
> functionality in
> an extension called SelectResults which can be used as a near drop in
> replacement.

Yeah,we need this. A few months back, we were trying to reconcile the
differences between this paging implementation and that of
WebHelpers. I think this is a fine solution for now. Pagination also
needs docs so that we can declare it as a feature :)

Kevin



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears
-~----------~----~----~----~------~----~------~--~---

Attachment: paginate.py.diff
Description: Binary data

Attachment: paginate_datagrid.kid.diff
Description: Binary data

Reply via email to