Cool. Let's see if Postgres will decide to implement this one. We're 12 years on from 2011 with no implementation.
PostgreSQL already supports:
* ORDER BY in grouped table (F868)
* GREATEST and LEAST (T054)
* String padding functions (T055)
* Multi-character TRIM functions (T056)
* Optional string types maximum length (T081)
* Enhanced cycle mark values (T133)
* JSON data type (T801)
* Enhanced JSON data type (T802)
* String-based JSON (T803)
* SQL/JSON simplified accessor (T860–T864)
The upcoming release of PostgreSQL 16 will have:
* Non-decimal integer literals (T661)
* Underscores in numeric literals (T662)
PostgreSQL currently lacks:
* UNIQUE null treatment (F292)
* ANY_VALUE (T626)
* Hex integer literals in SQL/JSON path language (T840)
* SQL/JSON item methods (T865–T878)
* JSON comparison (T879–T882) - though the nonstandard JSONB has this
* Property Graph Queries
---
As with many standards, the SQL standard likes to include things that DBMSs already have in the wild and have found practically useful.
See the end of the documentation on unique constraints: https://www.postgresql.org/docs/15/ddl-constraints.html#DDL-...
I'm out of date :)
Where is the doc for this one? I can find Postgres’ own JSON(B) operators, as well as jsonpath (sql/json path language) support, but not SQL-level json paths, specifically the dot syntax.
Then there's the whole graph data stuff that seems to come straight from Oracle?