| 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 15:06:58 |
| Message-ID: | 414139.1784473618@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 2026-07-17 Fr 10:38 AM, Tom Lane wrote:
>> Yeah. It's annoying as heck, because they deprecated that without
>> providing an adequate replacement. The replacement is claimed to
>> be "Use the modern options API with XML_PARSE_NOBLANKS", but there
>> is no direct equivalent to xmlParseBalancedChunkMemory that takes
>> an options argument.
> 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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-07-19 16:33:56 | Re: Deprecation warnings on Rocky 10.2 with current dev branch |
| Previous Message | Andrew Dunstan | 2026-07-19 14:38:52 | Re: Deprecation warnings on Rocky 10.2 with current dev branch |