| From: | Chapman Flack <chap(at)anastigmatix(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, mostafa_bit0108(at)hotmail(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org, Markus Winand <markus(dot)winand(at)winand(dot)at>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Subject: | Re: BUG #16046: xpath returns CDATA tag along with the value in postgres 12 |
| Date: | 2019-10-25 01:45:44 |
| Message-ID: | 5DB253C8.4020501@anastigmatix.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 10/24/19 19:14, Chapman Flack wrote:
> Which may or may not be a good thing. Perhaps it could lead the unwary
> in some cases to think such a query is giving a directly usable
> text string back, which will be harmless until the one time a value
> with escaping comes back. (The no-surprises way to get back a directly
> usable text string, if that's what's wanted, would be with XMLTABLE
> and an output column of text type.)
If the original reporter is happy with getting xml back, instead of
raw text, but only wants the form of escaping to be the same as it was
in pg11, the xpath //cname/aname/text() can just be rewritten as
string(//cname/aname), which will lose any CDATA-ness and consistently
produce the form where individual characters are escaped, in 11 or 12.
I think.
Regards,
-Chap
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yuri Astrakhan | 2019-10-25 01:58:25 | Re: BUG #16076: JIT causes huge delays in a complex query. jit=off solves it. |
| Previous Message | Andres Freund | 2019-10-25 01:04:56 | Re: BUG #16076: JIT causes huge delays in a complex query. jit=off solves it. |