Re: BUG #8469: Xpath behaviour unintuitive / arguably wrong

=?iso-8859-5?B?stjb1d0gwtDc0d7S5tXS?= <v.tambovtsev@outlook.com> writes:

Any news on this bug? 9.4 still behaves wrong and this actively stops us from using Postgresql as a storage for our xml docs.

AFAICS the conclusion in that thread was that the current behavior is
correct; in particular xpath()'s output is still XML and so it must not
de-escape anything.

/messages/by-id/72DA66D9-0222-4888-AF55-61D3337CAC7A@phlo.org

regards, tom lane

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

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

--
Вилен Тамбовцев

----------------------------------------

From: tgl@sss.pgh.pa.us
To: v.tambovtsev@outlook.com
CC: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #8469: Xpath behaviour unintuitive / arguably wrong
Date: Tue, 3 Feb 2015 17:09:34 -0500

=?iso-8859-5?B?stjb1d0gwtDc0d7S5tXS?= <v.tambovtsev@outlook.com> writes:

Any news on this bug? 9.4 still behaves wrong and this actively stops us from using Postgresql as a storage for our xml docs.

AFAICS the conclusion in that thread was that the current behavior is
correct; in particular xpath()'s output is still XML and so it must not
de-escape anything.

/messages/by-id/72DA66D9-0222-4888-AF55-61D3337CAC7A@phlo.org

regards, tom lane

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/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.

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Well, I had a conversation with Bruce Momjian he said that they added this bug to TODO list.
Almost 2 years has passed since and the bug is still here.
IMO this bug is actually a blocker for XML code part since xpath is core functionality.

--
Вилен Тамбовцев