Subject: Re: Encoding problems in PostgreSQL with XML data
From: Hannu Krosing <hannu@tm.ee>
To: Merlin Moncure <merlin.moncure@rcsonline.com>
Cc: pgsql-hackers@postgresql.org
In-Reply-To: <303E00EBDD07B943924382E153890E5434AA4F@cuthbert.rcsinc.local>
References: <303E00EBDD07B943924382E153890E5434AA4F@cuthbert.rcsinc.local>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1073997761.2528.8.camel@fuji.krosing.net>
Mime-Version: 1.0
Date: Tue, 13 Jan 2004 14:42:41 +0200

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