Check if items is a sqlalchemy query would be an immediate fix.
This can seriously kill a web server so paginate should be considered
unusable with sqlalchemy until this is resolved.
On 20 Mar 2011 08:04, Mike Orr sluggos...@gmail.com wrote:
I got this bug report in WebHelpers 1.3b1:
On Sat,
On 3/20/11 09:04 , Mike Orr wrote:
I got this bug report in WebHelpers 1.3b1:
On Sat, Mar 19, 2011 at 9:36 PM, Bitbucketissues-nore...@bitbucket.org wrote:
New issue 63: Regression: paginate loads whole table when given SqlAlchemy
object
On Sun, Mar 13, 2011 at 12:32 AM, Eric Ongerth ericonge...@gmail.comwrote:
+1. If I chose Pylons over Django and TurboGears (not to mention
Rails) for its flexibility, light weight, and pluggability, Pyramid
offers more of those qualities than Pylons and with better docs, plus
built-in
This issue has been previously discussed, I just wanted to make sure
that everyone agrees. At the moment the docs refer to paster
templates and renderered templates(mako, chameleon, jinja) using the
same name. I propose that we change the official nomenclature used to
describe paster templates
Fine by me.
- C
On Sun, 2011-03-20 at 22:12 -0500, Joe Dallago wrote:
This issue has been previously discussed, I just wanted to make sure
that everyone agrees. At the moment the docs refer to paster
templates and renderered templates(mako, chameleon, jinja) using the
same name. I propose
On Sun, Mar 20, 2011 at 6:38 AM, Wichert Akkerman wich...@wiggy.net wrote:
New issue 63: Regression: paginate loads whole table when given
SqlAlchemy object
Yaiks - that change will effectively kill any site which does pagination
over a large SQL table, so reverting it would be a good start.
