| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Steve Prentice" <prentice(at)cisco(dot)com>, "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, "Bernd Helmle" <mailings(at)oopsware(dot)de>, "PostgreSQL-development Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: mixed, named notation support |
| Date: | 2009-08-10 17:55:44 |
| Message-ID: | 4A8018D00200002500029780@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Sun, Aug 9, 2009 at 12:27 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Now that I've started to read this patch ... exactly what is the
>> argument for allowing a "mixed" notation (some of the parameters
>> named and some not)? ISTM that just serves to complicate both the
>> patch and the user's-eye view, for no real benefit.
>
> Wow, I can't imagine not supporting that. Doesn't every language
> that supports anything like named parameters also support a mix?
Sybase ASE and Microsoft SQL Server support mixed notation (and I
think that goes back to their common version 1.0). If a parameter is
specified more than once, it is an error.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brendan Jurd | 2009-08-10 17:56:08 | Re: WIP: to_char, support for EEEE format |
| Previous Message | Alvaro Herrera | 2009-08-10 17:55:07 | Re: WIP: to_char, support for EEEE format |