Re: django 1.0.2, django_pagination-1.0.5, postgresql, LIMIT & OFFSET question

Karen Tracey pisze: > On Wed, Feb 4, 2009 at 3:01 AM, Bartek SQ9MEV > wrote: [...] > So, any idea where's the clue? > Is it possible to use django-pagination with generic views without so > senseless overhead? > The cause was the {% if

Re: django 1.0.2, django_pagination-1.0.5, postgresql, LIMIT & OFFSET question

On Wed, Feb 4, 2009 at 3:01 AM, Bartek SQ9MEV wrote: > > Bartek pisze: > > > so... looks like everytime I need 20 Post items my database is hit by > > query returning all records... I find it a big overhead, and my app > > suffers from that... > Today I'm still investigating

Re: django 1.0.2, django_pagination-1.0.5, postgresql, LIMIT & OFFSET question

Bartek pisze: > so... looks like everytime I need 20 Post items my database is hit by > query returning all records... I find it a big overhead, and my app > suffers from that... Today I'm still investigating this issue, and I've just tried to use Paginator object as described at

django 1.0.2, django_pagination-1.0.5, postgresql, LIMIT & OFFSET question

Hi all Using django-pagination, I encounter some serious performance problems related to django-pagination. Request for every page triggers sql query returning all Post instances, here's detailed description of my problem: My model Is: class Post(models.Model): group =