On Apr 7, 2011, at 6:58 PM, Tom Lane wrote: > Well, if we're going to consider 100% backwards compatibility a "must", > then we should just stick with what the submitted patch does, ie, > unqualified names are matched first to query columns, and to parameters > only if there's no column match. This is also per spec if I interpreted > Peter's comments correctly. The whole thread started because I > suggested that throwing an error for ambiguous cases might be a better > design in the long run, but apparently long term ease of code > maintenance is far down our list of priorities ...
I agree with you that it should throw an error, at least optionally. Could we not recycle the settings that control this for plpgsql functions? Best, David -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
