Doc Rework: Section 9.16.13 SQL/JSON Query Functions
David G. Johnston <david.g.johnston@gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-06-25T06:46:40Z
Lists: pgsql-hackers
Attachments
- v2-0001-doc-json-query_9-16-3.patch (application/octet-stream) patch v2-0001
Hey! Lots of SQL/JSON threads going about. This one is less about technical correctness and more about usability of the documentation. Though in writing this I am finding some things that aren't quite clear. I'm going to come back with those on a follow-on post once I get a chance to make my second pass on this. But for the moment just opening it up to a content and structure review. Please focus on the text changes. It passes "check-docs" but I still need to work on layout and stuff in html (markup, some more links). Thanks! David J. p.s. v1 exists here (is just the idea of using basically variable names in the function signature and minimizing direct syntax in the table); https://www.postgresql.org/message-id/CAKFQuwbYBvUZasGj_ZnfXhC2kk4AT%3DepwGkNd2%3DRMMVXkfTNMQ%40mail.gmail.com
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
SQL/JSON: Various improvements to SQL/JSON query function docs
- ce416fadb4b6 17.0 landed
- 42de72fa7b80 18.0 landed