From: | Jaime Casanova <systemguards(at)yahoo(dot)com> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Rewritten queries |
Date: | 2004-12-27 19:48:45 |
Message-ID: | 20041227194845.86489.qmail@web50008.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
--- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> escribió:
> Jaime Casanova <systemguards(at)yahoo(dot)com> writes:
> > What version of postgres are u using?
> > I don't see that particular behavior in coalesce.
>
> > someone knows if this is the behavior in any older
> > version of pg?
>
> Yes. Since about 7.4 COALESCE is a first-class
> expression node type,
> but before that the parser expanded it into a CASE
> construct.
>
> The CASE implementation is lacking in that it may
> evaluate the arguments
> more than once, which could be wrong if they are
> volatile values.
>
> regards, tom lane
>
So, i think the recommended suggestion will be to
upgrade to a newer version. Maybe you want to wait
until 8 is out.
regards,
Jaime Casanova
_________________________________________________________
Do You Yahoo!?
Información de Estados Unidos y América Latina, en Yahoo! Noticias.
Visítanos en http://noticias.espanol.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2004-12-27 21:03:48 | Re: Extracting data where a column is max |
Previous Message | Tom Lane | 2004-12-27 19:42:25 | Re: Rewritten queries |