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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Вилен Тамбовцев <v(dot)tambovtsev(at)outlook(dot)com>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #8469: Xpath behaviour unintuitive / arguably wrong
Date: 2015-02-03 22:09:34
Message-ID: 32403.1423001374@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

=?iso-8859-5?B?stjb1d0gwtDc0d7S5tXS?= <v(dot)tambovtsev(at)outlook(dot)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.

http://www.postgresql.org/message-id/72DA66D9-0222-4888-AF55-61D3337CAC7A@phlo.org

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Вилен Тамбовцев 2015-02-03 22:13:03 Re: BUG #8469: Xpath behaviour unintuitive / arguably wrong
Previous Message Вилен Тамбовцев 2015-02-03 15:49:18 Re: BUG #8469: Xpath behaviour unintuitive / arguably wrong