| From: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #8469: Xpath behaviour unintuitive / arguably wrong |
| Date: | 2015-02-04 06:22:54 |
| Message-ID: | 1423030974840-5836676.post@n5.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Вилен Тамбовцев-2 wrote
> Actually, xpath()'s output is not original XML, at least there must be a
> function like XML_UNESCAPE() for current behavior
> otherwise there is no way to get proper xml with xpath
Based upon the link provided this has been acknowledged.
My personal opinion is that this is a bug (via omission) that the patch
introduced and that said patch author or committer should work to rectify.
Our XML/xpath handling is a large brick shy of a load if we do not provide a
way to make Unescaped text extraction possible.
David J.
--
View this message in context: http://postgresql.nabble.com/Re-BUG-8469-Xpath-behaviour-unintuitive-arguably-wrong-tp5836629p5836676.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Вилен Тамбовцев | 2015-02-04 08:13:44 | Re: BUG #8469: Xpath behaviour unintuitive / arguably wrong |
| Previous Message | Sandeep Thakkar | 2015-02-04 06:20:26 | Re: PostgreSQL - Installation on Windows 8 - I need help |