On Jul24, 2011, at 01:25 , Florian Pflug wrote:
> On Jul23, 2011, at 22:49 , Peter Eisentraut wrote:
>
>> On lör, 2011-07-23 at 17:49 +0200, Florian Pflug wrote:
>>> The current thread about JSON and the ensuing discussion about the
>>> XML types' behaviour in non-UTF8 databases made me try out ho
On Jul23, 2011, at 22:49 , Peter Eisentraut wrote:
> On lör, 2011-07-23 at 17:49 +0200, Florian Pflug wrote:
>> The current thread about JSON and the ensuing discussion about the
>> XML types' behaviour in non-UTF8 databases made me try out how well
>> XPATH() copes with that situation. The code,
On lör, 2011-07-23 at 17:49 +0200, Florian Pflug wrote:
> The current thread about JSON and the ensuing discussion about the
> XML types' behaviour in non-UTF8 databases made me try out how well
> XPATH() copes with that situation. The code, at least, looks
> suspicious - XPATH neither verifies tha
[Resent with pgsql-hackers re-added to the recipient list.
I presume you didn't remove it on purpose]
On Jul23, 2011, at 18:11 , Joey Adams wrote:
> On Sat, Jul 23, 2011 at 11:49 AM, Florian Pflug wrote:
>> So what I think we should do is tell libxml that the encoding is ASCII
>> if the server en
Hi
The current thread about JSON and the ensuing discussion about the
XML types' behaviour in non-UTF8 databases made me try out how well
XPATH() copes with that situation. The code, at least, looks
suspicious - XPATH neither verifies that the server encoding is UTF-8,
not does it pass the server
