| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: json api WIP patch |
| Date: | 2013-02-04 14:18:04 |
| Message-ID: | CAHyXU0zgokK_U=cjKqruTtdjuk72DxkszBkSHpWxEDf=Ck=u6A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Feb 1, 2013 at 4:08 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> But even leaving that aside, I'm surprised to hear so many people
> dismissing SQL standards compliance so blithely. We've certainly
> spent a lot of blood, sweat, and tears on minor standards-compliance
> issues over they years - why is it OK to not care about this
> particular issue when we've spent so much effort caring about other
> ones?
Does the SQL Standard suggest you can't extend the language with
operators? Or does it reserve certain characters for future use? And
if so, is there a list?
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2013-02-04 14:23:31 | Re: ALTER command reworks |
| Previous Message | Alvaro Herrera | 2013-02-04 14:13:26 | Re: [PATCH] Add PQconninfoParseParams and PQconninfodefaultsMerge to libpq |