| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Deprecation warnings on Rocky 10.2 with current dev branch |
| Date: | 2026-07-19 16:33:56 |
| Message-ID: | 484621.1784478836@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> I think we can probably use xmlParseInNodeContext(), which does take an
>> options argument. Did you look at that?
> Hmm ... I think I was confused by the fact that it takes "const char
> *data" not "const xmlChar *string". On further research, those are
> more equivalent than I'd thought. So maybe it'll work.
Here's a quick draft that passes check-world, which is enough to give
me no faith whatsoever. Maybe somebody who knows XML better than me
can break it. One thing I'm pretty unsure about is having to cons up
a dummy root node, which is necessary because xmlParseInNodeContext
takes a parent node not a parent doc. Is that correct? In the case
where we don't call xmlParseInNodeContext because the string is empty,
should we still make that node or just leave the document root-less?
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-avoid-xmlKeepBlanksDefault.patch | text/x-diff | 5.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-07-19 18:30:40 | Re: Deprecation warnings on Rocky 10.2 with current dev branch |
| Previous Message | Tom Lane | 2026-07-19 15:06:58 | Re: Deprecation warnings on Rocky 10.2 with current dev branch |