On Fri, 28 Oct 2005 03:03 pm, Tom Lane wrote:
> Philip Yarra <[EMAIL PROTECTED]> writes:
> > Hmmm... is it feasible to make the error message a little more useful?
> > People who didn't use the old-style positional parameters might not
> > understand where $1 and $2 are coming from.
>
> Not sure how --- the arm's-length relationship between plpgsql and the
> main parser hurts us here.
Yeah, I had a suspicion the answer might be along those lines.
Well, here's a minor doco patch against HEAD to at least record this with the
Oracle PL/sql -> PL/pgSQL porting notes.
Regards, Philip.
-----------------
Utiba Pty Ltd
This message has been scanned for viruses and
dangerous content by Utiba mail server and is
believed to be clean.
Index: doc/src/sgml/plpgsql.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/plpgsql.sgml,v
retrieving revision 1.79
diff -c -r1.79 plpgsql.sgml
*** doc/src/sgml/plpgsql.sgml 21 Oct 2005 05:11:23 -0000 1.79
--- doc/src/sgml/plpgsql.sgml 28 Oct 2005 05:20:54 -0000
***************
*** 3132,3137 ****
--- 3132,3144 ----
state in temporary tables, instead.
</para>
</listitem>
+ <listitem>
+ <para>
+ You cannot use parameter names that are the same as columns
+ that are referenced in the function. Oracle does allow you to do this
+ if you qualify the parameter name as function_name.paramater_name
+ </para>
+ </listitem>
</itemizedlist>
</para>
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
