From: silly sad <sad@bankir.ru>
To: pgsql-sql@postgresql.org
Subject: Re: best paging strategies for large datasets?
Date: Thu, 13 May 2010 12:41:30 +0400
Message-ID: <4BEBBB3A.1060104@bankir.ru> (raw)
In-Reply-To: <20100513074712.GB19779@apartia.fr>
References: <20100512054144.GA8762@apartia.fr>
<4BEBAC15.4030105@bankir.ru>
<20100513074712.GB19779@apartia.fr>
>> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: sad@bankir.ru
Subject: Re: best paging strategies for large datasets?
In-Reply-To: <4BEBBB3A.1060104@bankir.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox