Re: XMLSerialize: version and explicit XML declaration

From: Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: XMLSerialize: version and explicit XML declaration
Date: 2025-02-21 09:33:32
Message-ID: 6793f32a-1796-40db-a7f0-1496f369bf1a@uni-muenster.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 30.09.24 10:08, Jim Jones wrote:
> On 25.09.24 18:02, Tom Lane wrote:
>> AFAICS, all we do with an embedded XML version string is pass it to
>> libxml2's xmlNewDoc(), which is the authority on whether it means
>> anything. I'd be inclined to do the same here.
> Thanks. I used xml_is_document(), which calls xmlNewDoc(), to check if
> the returned document is valid or not. It then decides if an unexpected
> version deserves an error or just a warning.
>
> Attached v1 with the first attempt to implement these features.

rebase

Best regards, Jim

Attachment Content-Type Size
v2-0001-Add-XMLSerialize-explicit-XML-declaration-SQL-XML.patch text/x-patch 57.8 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2025-02-21 09:36:07 Re: Missing [NO] INDENT flag in XMLSerialize backward parsing
Previous Message Andrew Dunstan 2025-02-21 09:32:20 Re: TAP test started using meson, can get a tcp port already used by another test.