Em Terça 02 Maio 2006 11:22, Kevin Dangoor escreveu: > > I think the way to handle this, if we decide it's necessary at some > point, is to do it the way the search engines do. Hang on to a list of > the first N results (you don't hold all the data, just a reference -- > like the ids, or depending on your app, maybe you hold on to the data > that will be in the grid) and page through that. The key here is that
I was going to say something like that before, but then I remembered Google and the way it "narrows" results if they are similar to the ones already displayed. It is not uncommon to start a search and see something like "7" pages available and when you go to the second it is the last one and you see the message that other results are similar to the ones already shown and to show them you should click on the link. > it's probably application dependent, and pagination will likely need > to support (ultimately) different ways of getting at the data. Indeed. Specially because after I looked at the patch I saw that it is SQL Object specific, with no support for SQL Alchemy... This should also be a problem for the future if we change ORMs. > It also occurs to me that the decorator-based pagination only supports > the notion of a page where you have one bit of pagination going on and > nothing else really happening (unless you use ajax). Yep. It only paginates. :-) It doesn't sort, etc. > It's okay to have limitation in a first take of something, but it's > good to be aware of what those limitations are. If it is documented, then it is not a bug ;-) -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk -~----------~----~----~----~------~----~------~--~---
