Re: XML only working in UTF-8 - Re: 8.4 open items list

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Chris Browne <cbbrowne(at)acm(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>
Subject: Re: XML only working in UTF-8 - Re: 8.4 open items list
Date: 2009-04-05 21:09:31
Message-ID: 200904060009.33425.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sunday 05 April 2009 05:00:04 Tom Lane wrote:
> Chris Browne <cbbrowne(at)acm(dot)org> writes:
> > josh(at)agliodbs(dot)com (Josh Berkus) writes:
> >> This one is also really bad, but probably only Doc-patchable.
> >> However, can SQL/XML really be said to be core functionality if it
> >> only works in UTF-8?
> >> * BUG #4622: xpath only work in utf-8 server encoding
> >
> > Well, much of the definition of XML assumes the use of Unicode, so I
> > don't feel entirely badly about there being such a restriction.
> >
> > It seems likely to me that opening its use to other encodings has a
> > considerable risk of breaking due to a loss of, erm, "closure," in the
> > mathematical sense. Or, alternatively, opening a Pandora's Box of
> > needing to do translations to prevent mappings from breaking.
>
> Is there a reason not to fix it as suggested at
> http://archives.postgresql.org/pgsql-bugs/2009-02/msg00032.php
> ie recode on-the-fly from database encoding to UTF8?

Probably just verifying that it works.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zdenek Kotala 2009-04-05 21:21:47 Re: Solaris getopt_long and PostgreSQL
Previous Message Tom Lane 2009-04-05 20:05:52 Re: EXPLAIN WITH