| From: | solai v <solai(dot)cdac(at)gmail(dot)com> |
|---|---|
| To: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> |
| Cc: | newtglobal postgresql_contributors <postgresql_contributors(at)newtglobalcorp(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Subject: | Re: Add XMLNamespaces to XMLElement |
| Date: | 2026-08-17 06:12:37 |
| Message-ID: | CAF0whuf1JMg3f5Z9fSYA0aqnN2ckFy=YKhvqwsu1_n93=H9jtQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
I tested the patch for adding XMLNamespaces support to XMLELEMENT.
I checked the following cases:
Basic XMLELEMENT() continues to work.
Namespace with a prefix works correctly.
DEFAULT namespace works correctly.
NO DEFAULT works correctly.
Multiple namespace declarations work as expected.
Nested namespaces are handled correctly.
I also tested XMLTABLE with NO DEFAULT.
For example:
SELECT xmlelement(
NAME "foo",
xmlnamespaces('http://x.y' AS bar)
);
returns:
<foo xmlns:bar="http://x.y"/>
I also tested the nested namespace case and got the expected result:
<root xmlns="http://x.y/ns1">
<foo xmlns=""/>
</root>
Overall, the tested cases are working as expected, and I did not
notice any issues during testing.
Regards,
Solai
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrei Lepikhov | 2026-08-17 06:13:29 | Allow a prosupport function to be attached to an aggregate |
| Previous Message | Andrey Rachitskiy | 2026-08-17 06:05:56 | Re: Residual cleanups for tied objects in PL/Perl |