On 11/10/07, Tom Lane [EMAIL PROTECTED] wrote:
The current plpgsql code seems to be designed to force a qualifier to be
interpreted as a block label if at all possible, even if there are
more-closely-nested alternative interpretations; so in the above example
it would assign to the outer
Marko Kreen [EMAIL PROTECTED] writes:
On 11/10/07, Tom Lane [EMAIL PROTECTED] wrote:
Can anyone comment on how Oracle handles cases like this?
Some googling brought following link:
http://download-uk.oracle.com/docs/cd/B14117_01/appdev.101/b10807/d_names.htm
Hmm, interesting document. I
I stumbled on another gotcha in 8.3's plpgsql:
create or replace function foobar() returns text as $$
declare
foobar text;
begin return 'ok'; end;
$$ language plpgsql;
Results in error:
ERROR: syntax error at or near foobar
LINE 3: foobar text;
^
If this is intentional,
On 10/11/2007, Marko Kreen [EMAIL PROTECTED] wrote:
I stumbled on another gotcha in 8.3's plpgsql:
create or replace function foobar() returns text as $$
declare
foobar text;
begin return 'ok'; end;
$$ language plpgsql;
Results in error:
ERROR: syntax error at or near foobar
Pavel Stehule [EMAIL PROTECTED] writes:
On 10/11/2007, Marko Kreen [EMAIL PROTECTED] wrote:
I stumbled on another gotcha in 8.3's plpgsql:
It's label for function's parameters.
But now that you mention it, that behavior is a little bit ugly.
I believe it's a pretty common practice to use a
