From: | Chapman Flack <jcflack(at)acm(dot)org> |
---|---|
To: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Robert Treat <rob(at)xzilla(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: XMLDocument (SQL/XML X030) |
Date: | 2025-01-24 16:18:51 |
Message-ID: | 6793BD6B.5050301@acm.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 01/24/25 10:49, Chapman Flack wrote:
> The SQL-standard `XMLDOCUMENT` function applied to an XML value
> /expr/ has effects equivalent to the XML Query expression
> `document { /expr/ }`, specified to replace any document nodes
> in the input with their children and wrap the whole result in one
> document node. An XML Query "document node" is a relaxed version
> of XML document structure, which need not have exactly one child
> element node, and also allows text nodes as children.
Or even: ... An XML Query "document node" is a relaxed version
of XML document structure that corresponds exactly to what
PostgreSQL's one XML type is already allowed to contain, so
any non-null PostgreSQL XML value can be returned unchanged.
More-permissive XML types some systems offer may hold values
that are not so structured.
Regards,
-Chap
From | Date | Subject | |
---|---|---|---|
Next Message | Corey Huinker | 2025-01-24 16:19:12 | Re: vacuumdb changes for stats import/export |
Previous Message | Ashutosh Sharma | 2025-01-24 16:04:58 | Re: Orphaned users in PG16 and above can only be managed by Superusers |