Subject: Re: Encoding problems in PostgreSQL with XML data
From: Hannu Krosing <hannu@tm.ee>
To: Merlin Moncure <merlin.moncure@rcsonline.com>
Cc: Peter Eisentraut <peter_e@gmx.net>, pgsql-hackers@postgresql.org
In-Reply-To: <303E00EBDD07B943924382E153890E5434AA48@cuthbert.rcsinc.local>
References: <303E00EBDD07B943924382E153890E5434AA48@cuthbert.rcsinc.local>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1073775784.3542.3.camel@fuji.krosing.net>
Mime-Version: 1.0
Date: Sun, 11 Jan 2004 01:03:04 +0200

Merlin Moncure kirjutas R, 09.01.2004 kell 22:04:
> Peter Eisentraut wrote:
> > The central problem I have is this:  How do we deal with the fact that
> > an XML datum carries its own encoding information?
> 
> Maybe I am misunderstanding your question, but IMO postgres should be
> treating xml documents as if they were binary data, unless the server
> takes on the role of a parser, in which case it should handle
> unspecified/unknown encodings just like a normal xml parser would (and
> this does *not* include changing the encoding!).
> 
> According to me, an XML parser should not change one bit of a document,
> because that is not a 'parse', but a 'transformation'.

IIRC, the charset transformations are done as a separate step in the
wire protocol _before_ any parser has chance transform or not.

The charset transform on incoming query are also agnostic of text
contents - it just blindly transforms the whole SQL statement.

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