Re: SQL/JSON revisited
Jonathan S. Katz <jkatz@postgresql.org>
From: "Jonathan S. Katz" <jkatz@postgresql.org>
To: Nikita Malakhov <hukutoc@gmail.com>,
Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Amit Langote <amitlangote09@gmail.com>,
Alexander Lakhin <exclusion@gmail.com>, Erik Rijkers <er@xs4all.nl>,
Andrew Dunstan <andrew@dunslane.net>,
Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
Andres Freund <andres@anarazel.de>, vignesh C <vignesh21@gmail.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>,
e.indrupskaya@postgrespro.ru
Date: 2023-04-04T19:44:05Z
Lists: pgsql-hackers
On 4/4/23 3:40 PM, Nikita Malakhov wrote: > Hi hackers! > > The latest SQL standard contains dot notation for JSON. Are there any > plans to include it into Pg 16? > Or maybe we should start a separate thread for it? I would recommend starting a new thread to discuss the dot notation. Thanks, Jonathan
Commits
-
Add SQL/JSON query functions
- 6185c9737cf4 17.0 landed
-
Add soft error handling to some expression nodes
- aaaf9449ec6b 17.0 landed
-
Adjust populate_record_field() to handle errors softly
- 1edb3b491bee 17.0 landed
-
Refactor code used by jsonpath executor to fetch variables
- faa2b953ba3b 17.0 landed
-
Code review for recent SQL/JSON commits
- 71bfd1543f8b 16.0 landed
-
Fix inconsistencies and style issues in new SQL/JSON code
- 60966f56c3e4 16.0 landed
-
Don't install postmaster symlink anymore
- 37e267335068 16.0 cited
-
Revert SQL/JSON features
- 2f2b18bd3f55 16.0 cited
-
Doc: standardize markup a bit more.
- 47046763c3ed 13.0 cited