From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Emanuel Calvo Franco <postgres(dot)arg(at)gmail(dot)com> |
Cc: | postgresql Forums <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: limit-offset different result sets with same query |
Date: | 2009-05-09 01:59:37 |
Message-ID: | 20090509015937.GT18067@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, May 08, 2009 at 06:40:33PM -0300, Emanuel Calvo Franco wrote:
> 2009/5/8 David Fetter <david(at)fetter(dot)org>:
> > On Fri, May 08, 2009 at 06:10:18PM -0300, Emanuel Calvo Franco wrote:
> >> Hi all.
> >>
> >> I'll make this faster.
> >>
> >> I hace this table and this function:
> >
> > You should only ever assume that your SELECT's output will have a
> > particular ordering when you include an ORDER BY clause that
> > actually specifies the order well enough :)
> >
>
> I test it in the first time :)
>
> With the 'order by' it works well, but in 'theory'
The theory under which you should operate is that the underlying
implementation only gives you the orderings you ask for. This way,
when other beneficial implementation changes happen, they will not
surprise you. :)
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas | 2009-05-09 08:14:49 | Re: Remote access |
Previous Message | bfriedman.postgresql | 2009-05-09 01:47:48 | Re: Column oriented pgsql |