From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Oliver Elphick" <olly(at)lfix(dot)co(dot)uk> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Is this a bug in 7.1? |
Date: | 2001-03-13 15:29:06 |
Message-ID: | 19350.984497346@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Oliver Elphick" <olly(at)lfix(dot)co(dot)uk> writes:
> bray=# SELECT DISTINCT p.id, p.name, a.town
> bray-# FROM (
> bray(# SELECT id, name
> bray(# FROM customer
> bray(# UNION
> bray(# SELECT id, name
> bray(# FROM supplier
> bray(# ) AS p
> bray-# LEFT OUTER JOIN address AS a
> bray-# ON p.address = a.id
> bray-# WHERE p.id = '22002';
> ERROR: function applied to tuple is not supported for subSELECTs
> What does the error message mean?
table.functionname is an ancient PostQUEL notation for functions that
take whole tuples --- think "address(p)" and you'll have a better idea
what the parser is seeing here.
This notation is something we're probably going to have to retire soon,
since I doubt it will play well with schema notation (too hard to guess
what foo.bar.baz means). I doubt anyone but the regression tests still
use the PostQUEL notation for function calls anyway.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jean-Christophe Boggio | 2001-03-13 15:54:00 | Where's that doc on plans ? |
Previous Message | Alex Howansky | 2001-03-13 15:23:10 | Re: "critical mass" reached? |