| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Joshua Berkus <josh(at)agliodbs(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Matthew Draper <matthew(at)trebex(dot)net> |
| Subject: | Re: WIP: Allow SQL-language functions to reference parameters by parameter name |
| Date: | 2011-03-26 03:01:45 |
| Message-ID: | 28551.1301108505@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mar 25, 2011, at 9:22 PM, Joshua Berkus <josh(at)agliodbs(dot)com> wrote:
>> 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.
Yes, a function that previously worked might now throw error, if we make
ambiguous names be errors. But this is *not* a failure that would occur
during dump/reload. You'd have to actually run the function.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2011-03-26 03:05:50 | Re: WIP: Allow SQL-language functions to reference parameters by parameter name |
| Previous Message | Robert Haas | 2011-03-26 02:45:13 | Re: WIP: Allow SQL-language functions to reference parameters by parameter name |