Re: WIP: Allow SQL-language functions to reference parameters by parameter name
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Joshua Berkus <josh@agliodbs.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Matthew Draper <matthew@trebex.net>
Date: 2011-03-26T02:45:13Z
Lists: pgsql-hackers
On Mar 25, 2011, at 9:22 PM, Joshua Berkus <josh@agliodbs.com> wrote: > Tom, > >> Personally I'd vote for *not* having any such dangerous semantics as >> that. We should have learned better by now from plpgsql experience. >> I think the best idea is to throw error for ambiguous references, >> period. > > As a likely heavy user of this feature, I agree with Tom here. I really don't want the column being silently preferred in SQL functions, when PL/pgSQL functions are throwing an error. I'd end up spending hours debugging this. > > Also, I don't understand why this would be a dump/reload issue if $1 and $2 continue to work. > Because an identifier that previously referred unambiguously to a column might now be ambiguous, if there is a parameter with the same name. ...Robert