| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Bernd Helmle <mailings(at)oopsware(dot)de>, Steve Prentice <prentice(at)cisco(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: mixed, named notation support |
| Date: | 2009-08-10 07:08:27 |
| Message-ID: | 162867790908100008k6344b565hfbaeb03c06f275cf@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
>> Considering that we are worried about someday having to adjust to a
>> SQL standard in this area, I think we ought to be as conservative as
>> possible about what we introduce as user-visible features here.
>> As an example, if they do go with "=>" as the parameter marker,
>> mixed notation would become a seriously bad idea because it would be
>> impossible to distinguish incidental use of => as an operator from
>> mixed notation.
>
I thing, so ANSI will be in conformance with Oracle - so I'll try to
check the possibility of the using => as any operator in Oracle
regards
Pavel Stehule
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-08-10 07:24:31 | Re: [COMMITTERS] pgsql: Ship documentation without intermediate tarballs Documentation |
| Previous Message | Pavel Stehule | 2009-08-10 07:04:54 | Re: mixed, named notation support |