| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | "George Henry C(dot) Daswani" <gdaswani(at)esri(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Problem with coalesce.. |
| Date: | 2000-11-01 16:50:06 |
| Message-ID: | Pine.BSF.4.10.10011010846000.69236-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general 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(at)bigpanda(dot)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
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2000-11-01 17:07:11 | Re: Array Problem |
| Previous Message | Louis-David Mitterrand | 2000-11-01 16:38:36 | a web interface to visualize tables |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2000-11-01 17:01:28 | Re: Outer Joins |
| Previous Message | Continuing Technical Education | 2000-11-01 15:01:22 | Re: Problem with coalesce.. |