I still don't know which is the bit that is syntactically not correct
> that a column name is a qualified reference to the function's OUT
parameter or
> that the function name is also a table alias
and the error message is not very helpful to find this out.
But I certainly l learned that I shoul
Balazs Klein writes:
> CREATE OR REPLACE FUNCTION instreq(OUT instreq_id integer)
> ...
> Select instreq.instreq_id From aaa instreq
The problem that you've got here is that instreq.instreq_id is in fact
a qualified reference to the function's OUT parameter. We didn't
support qualification of fu
Hi,
the test case below runs fine for me if the function name is not instreq and
returns an error if it is.
Regards.
Balazs
CREATE TABLE aaa (
instreq_id integer
);
INSERT INTO aaa (instreq_id) VALUES (223);
INSERT INTO aaa (instreq_id) VALUES (224);
INSERT INTO aaa (instreq_id) VALUES (2
"Balazs Klein" writes:
> On 8.4.1 on windows XP running the function gives an error message
> (Undefined column: 7 ERROR: record "rec" has no field "instreq_id") wich is
> strange because the underlying query does return that column.
There's really no way to investigate that without a *complete*
The following bug has been logged online:
Bug reference: 5108
Logged by: Balazs Klein
Email address: balazs.kl...@gmail.com
PostgreSQL version: 8.4.1
Operating system: Windows XP
Description:plpgsql function name conflict with table alias
Details:
I have a plpgsql f
