| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Asko Oja <ascoja(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Out parameters handling |
| Date: | 2009-03-07 01:44:35 |
| Message-ID: | 49B1D183.5030203@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert,
> I wonder whether it would be possible to make PL/pgsql take :foo to
> mean the parameter named foo, and then provide an option to make that
> THE ONLY WAY to refer to the parameter foo. For
> backward-compatibility, and compatibility with (ahem) other database
> products, we probably don't want to remove the option to have foo
> mean... any damn thing named foo you can put your hands on. But it
> would be nice to at least have the option of disabling that behavior
> when compatibility is not an issue, and correctness is.
Thing is, anybody can institute their own naming convention. I've long
used v_ as a prefix. Allowing : would save me some keystrokes, but
that's about it.
--Josh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-03-07 02:09:22 | pgsql: Avoid MSVC breakage caused by my previous commit by not using a |
| Previous Message | Robert Haas | 2009-03-07 01:41:44 | Re: Out parameters handling |