#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 | Keywords:
------------------------+---------------------------------------------------
With TG 1.0.4.4, my application runs great with this use of the paginate
decorator:
{{{
@paginate('updates', limit=20, allow_limit_override=True)
}}}
However, with TG 1.0.8, this behavior has changed, and the above example
completely ignores the `tg_paginate_limit` argument. This caused some
serious problems in our production environment, as *huge* datasets were
getting returned without being properly paginated.
To get it to obey the `tg_paginate_limit` required adding a `max_limit`
argument to the @paginate decorator, like so:
{{{
@paginate('updates', limit=20, max_limit=50,
allow_limit_override=True)
}}}
This sudden change in behaviour will probably cause problems for many. TG
1.0.8 throws the following deprecation warning
{{{
<string>:3: DeprecationWarning: allow_limit_override is deprecated. Use
max_limit to specify an upper bound for limit.
}}}
Yet, specifying max_limit without allow_limit_override does not seem to
allow for limit overrides...
--
Ticket URL: <http://trac.turbogears.org/ticket/2318>
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
-~----------~----~----~----~------~----~------~--~---
