From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Manfred Koizar <mkoi-pg(at)aon(dot)at>, pgsql-hackers(at)postgresql(dot)org, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: [HACKERS] plpgsql doesn't coerce boolean expressions to boolean |
Date: | 2003-09-09 17:57:23 |
Message-ID: | 200309091757.h89HvNi07005@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
Tom Lane wrote:
> Manfred Koizar <mkoi-pg(at)aon(dot)at> writes:
> > On Mon, 08 Sep 2003 11:40:32 -0400, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> > wrote:
> >> 4. Use the parser's coerce_to_boolean procedure, so that nonbooleans
> >> will be accepted in exactly the same cases where they'd be accepted
> >> in a boolean-requiring SQL construct (such as CASE). (By default,
> >> none are, so this isn't really different from #2. But people could
> >> create casts to boolean to override this behavior in a controlled
> >> fashion.)
>
> > I vote for 4.
>
> I'm willing to do that.
OK, what release should we do this?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-09-09 17:57:47 | Re: libpq++ |
Previous Message | Andrew Dunstan | 2003-09-09 17:51:11 | Re: plpgsql doesn't coerce boolean expressions to boolean |
From | Date | Subject | |
---|---|---|---|
Next Message | Roberto João Lopes Garcia | 2003-09-09 21:56:58 | Test, please ignore |
Previous Message | Andrew Dunstan | 2003-09-09 17:51:11 | Re: plpgsql doesn't coerce boolean expressions to boolean |