| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Oleg Bartunov <obartunov(at)gmail(dot)com>, Stefan Keller <sfkeller(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Forthcoming SQL standards about JSON and Multi-Dimensional Arrays (FYI) |
| Date: | 2016-07-06 04:17:35 |
| Message-ID: | CAFj8pRCx5j6GHm5SucKy9dVjNm20BnOJdHoft5cTf-kUgkajQA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2016-07-06 5:17 GMT+02:00 Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com
>:
> On 7/2/16 12:40 AM, Pavel Stehule wrote:
>
>> So ANSI SQL conform implementation of JSON support is still possible in
>> Postgres.
>>
>
> It is possible, but in this case I think it's not worth it. Our built-in
> stuff is significantly simpler and more powerful and already in widespread
> use.
>
I can't to agree. JSONPath is little bit powerful than our JSON path
expression. JSON_TABLE is pretty good function for extracting values from
JSON (note: I missing XML_TABLE too much).
More - Postgres is not famous due not respecting standard.
Regards
Pavel
>
> It is worth keeping an eye on it and not create gratuitous conflicts.
>
>
> --
> Peter Eisentraut http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-07-06 07:18:07 | Re: Password identifiers, protocol aging and SCRAM protocol |
| Previous Message | Greg Stark | 2016-07-06 03:32:03 | Re: can we optimize STACK_DEPTH_SLOP |