On Mar 25, 2011, at 9:22 PM, Joshua Berkus <j...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
