#2318: @paginate API breakage in 1.0.8
------------------------+---------------------------------------------------
Reporter: lmacken | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: TurboGears | Version: 1.0.8
Severity: major | Resolution:
Keywords: Patch |
------------------------+---------------------------------------------------
Comment (by toshio):
Thanks chrisz! The applied patch has one thing that seems odd to me but
it may be by design. If both allow_limit_override and max_limit are
specified and they are in conflict with each other the user is able to
override the default limit. My expectation is that max_limit would always
take precedence as it's the new way of doing things and
allow_limit_override is deprecated. Not a big deal as conflicts between
the two are obviously a mistake in the application code.
--
Ticket URL: <http://trac.turbogears.org/ticket/2318#comment:7>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---
