From: Rod Taylor <pg@rbt.ca>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: PostgreSQL Development <pgsql-hackers@postgresql.org>
Subject: Re: Encoding problems in PostgreSQL with XML data
Date: Fri, 09 Jan 2004 14:21:50 -0500
Message-ID: <1073676109.1521.18.camel@jester> (raw)
In-Reply-To: <200401091946.01930.peter_e@gmx.net>
References: <200401091946.01930.peter_e@gmx.net>
> Rewriting the <?xml?> declaration seems like a workable solution, but it
> would break the transparency of the client/server encoding conversion.
> Also, some people might dislike that their documents are being changed
> as they are stored.
I presume that the XML type stores the textual representation of the XML
rather than a binary (parsed) format?
I say we treat XML the same was as we deal with things like float and
allow some play with the stored object so long as it's reasonably small
and has the same final interpretation.
If they wanted non-mutable text, they would not have declared it as a
structured format. Just like if they don't want leading 0's removed from
numeric input, they don't declare it as numeric but as binary.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: pg@rbt.ca, peter_e@gmx.net
Subject: Re: Encoding problems in PostgreSQL with XML data
In-Reply-To: <1073676109.1521.18.camel@jester>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox