Re: [GENERAL] Problem with coalesce.. - Mailing list pgsql-sql

From Stephan Szabo
Subject Re: [GENERAL] Problem with coalesce..
Date
Msg-id Pine.BSF.4.10.10011010846000.69236-100000@megazone23.bigpanda.com
Whole thread Raw
In response to Problem with coalesce..  ("George Henry C. Daswani" <gdaswani@esri.com>)
Responses Re: Re: [GENERAL] Problem with coalesce..  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-sql
There are still some contexts in which subqueries in expressions are
wierd. The example below appears to work in current sources however.

Stephan Szabo
sszabo@bigpanda.com

On Tue, 31 Oct 2000, George Henry C. Daswani wrote:

> Hello,
>
>     Was wondering if such a call is unsupported, or a bug?
>
> 7.0.2 (postgresql, linux redhat 7.0)
>
> SELECT COALESCE ((SELECT NULL,1)
>
> returns a 1, correct..
>
> however..
>
> SELECT COALESCE ((SELECT CURVALUE FROM TABLEKEYS WHERE TABLENAME = 'BUYER'),1)
>
> returns a "UNKNOWN expression type 501"
>
> SELECT CURVALUE FROM TABLEKEYS WHERE TABLENAME = 'BUYER'; returns a '0'
>
> Thanks..
>
> George
>
>
>


pgsql-sql by date:

Previous
From: "Continuing Technical Education"
Date:
Subject: Re: Problem with coalesce..
Next
From: Josh Berkus
Date:
Subject: Re: Outer Joins