Re: Encoding problems in PostgreSQL with XML data - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: Encoding problems in PostgreSQL with XML data
Date
Msg-id 1073997761.2528.8.camel@fuji.krosing.net
Whole thread Raw
In response to Re: Encoding problems in PostgreSQL with XML data  ("Merlin Moncure" <merlin.moncure@rcsonline.com>)
Responses Re: Encoding problems in PostgreSQL with XML data  (Tatsuo Ishii <t-ishii@sra.co.jp>)
List pgsql-hackers
Merlin Moncure kirjutas E, 12.01.2004 kell 19:56:
> Hannu Krosing wrote:
> > IIRC, the charset transformations are done as a separate step in the
> > wire protocol _before_ any parser has chance transform or not.
> 
> Yep.  My point is that this is wrong.  

Of course :)

It seems to be a quick hack somebody implemented in need, and doing it
as a separate step was suely the easiest way to get it working.

I hope that real as-needed-column-by-column translation will be used
with bound argument queries.

It also seems possible to delegate the encoding changes to after the
query is parsed, but this will never work for EBCDIC and other funny
encodings (like rot13 ;). 

for these we need to define the actual SQL statement encoding on-wire to
be always ASCII.

---------------
Hannu



pgsql-hackers by date:

Previous
From: Claudio Natoli
Date:
Subject: Re: LWLock/ShmemIndex startup question
Next
From: "Merlin Moncure"
Date:
Subject: Re: [pgsql-hackers-win32] Win32 signal code - first try