Re: select question
От
Felipe Alvarez Harnecker
Тема
Re: select question
Дата
Msg-id
14725.54459.316287.652212@Lakgo.ql
Ответ на
Re: select question (Tom Lane)
Список
Дерево обсуждения
select question <database@gurubase.com>
Re: select question "Robert B. Easter" <reaster@comptechnews.com>
Re: select question Alfred Perlstein <bright@wintelcom.net>
Re: select question Ian Turner <vectro@pipeline.com>
Re: select question g <brian@wuwei.govshops.com>
Re: select question Tom Lane <tgl@sss.pgh.pa.us>
Re: select question Felipe Alvarez Harnecker <felipe@qlsoft.cl>
Re: select question Tom Lane <tgl@sss.pgh.pa.us>
Re: select question -- SOLVED Felipe Alvarez Harnecker <felipe@qlsoft.cl>
Tom Lane writes: > g writes: > > Use the limit clause. > > SELECT message_text FROM messages ORDER BY creation_date LIMIT $limit, > > $offset. > > > LIMIT 10, 0 gets you the first batch. > > LIMIT 10, 10 gets you the second batch. > > LIMIT 10, 20 gets you the third, etc. > > BTW, a little tip that a number of people have gotten burnt by not > knowing: when you do this you *must* use an ORDER BY clause that's > strong enough to order the result rows completely. Otherwise you > are asking for slices out of an undefined ordering of the rows. > You could get a different ordering on each request, leading to > inconsistent slices --- in other words, missing or repeated rows. > > This does actually happen in Postgres 7.0, because the planner > optimizes queries with small limit+offset differently from those > without. > > regards, tom lane Hi, I wonder if one must activate the LIMIT clause somewhere, bacause for me it does nothing. I'm using postgresql Version: 7.0.2 in a Debina potato system. Thanx. -- ______________________________________________________ Felipe Alvarez Harnecker. QlSoftware. Tel. 09.874.60.17 e-mail: felipe.alvarez@qlsoft.cl Potenciado por Debian GNU/Linux http://www.qlsoft.cl/ ______________________________________________________
В списке pgsql-general по дате отправления