On Jan 30, 7:11 am, Christoph Haas <[EMAIL PROTECTED]> wrote: > The webhelpers.pagination.paginate call fails miserably if an object > is given as the first parameter that is a proper SQLObject class or > SQLAlchemy query. The error message was "You shouldn't have this" > which doesn't tell the user what went wrong. And the error was > even passed back and displayed on the web page. So I thought raising > an exception might be a better way. Proposal
Yep, this is definitely a nicer message and makes it hard to miss if something goes wrong. I've merged this patch in the latest svn of WebHelpers. Thanks! - Ben --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
