Re: best paging strategies for large datasets?

From: silly sad <sad(at)bankir(dot)ru>
To: pgsql-sql(at)postgresql(dot)org
Subject: Re: best paging strategies for large datasets?
Date: 2010-05-13 08:41:30
Message-ID: 4BEBBB3A.1060104@bankir.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql


>> First u count(*) the rows and select a requested page
>> returning to a client the count result bundled "with a page of rows"
>>
>> (1) client renders the acquired rows
>> (2)__memorize__ what part of the data he just got
>> (3) and stores the count result to calculate "the pager div"
>>
>> all the subsequent clicks on "the pager div" should not immediately
>> generate requests and decides if the request is needed.
>
> Yes, rendering the results throught ajax is a good idea, but one has to
> be careful not to expose one's LIMIT and OFFSET to the client, but only
> the "page" number. Or else the client could query the whole data set. A
> lot of "professional" web site have that hole.
>

this is not a hole, it is only a matter of aesthetic

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Jasen Betts 2010-05-13 10:09:51 Re: Greetings folks, dumb question maybe?
Previous Message Louis-David Mitterrand 2010-05-13 07:47:13 Re: best paging strategies for large datasets?