From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | nikolay(at)samokhvalov(dot)com |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: xml type and encodings |
Date: | 2007-01-15 13:29:57 |
Message-ID: | 200701151429.58394.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Am Montag, 15. Januar 2007 12:42 schrieb Nikolay Samokhvalov:
> On 1/15/07, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> > Client encoding is A, server encoding is B. Client sends an xml datum
> > that looks like this:
> >
> > INSERT INTO table VALUES (xmlparse(document '<?xml version="1.0"
> > encoding="C"?><content>...</content>'));
> >
> > Assuming that A, B, and C are all distinct, this could fail at a number
> > of places.
> >
> > I suggest that we make the system ignore all encoding declarations in
> > xml data. That is, in the above example, the string would actually
> > have to be encoded in client encoding B on the client, would be
> > converted to A on the server and stored as such. As far as I can tell,
> > this is easily implemented and allowed by the XML standard.
>
> In other words, in case when B != C server must trigger an error, right?
No, C is ignored in all cases.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
From | Date | Subject | |
---|---|---|---|
Next Message | Gurjeet Singh | 2007-01-15 14:12:50 | Re: [PATCHES] [HACKERS] [Fwd: Index Advisor] |
Previous Message | Nikolay Samokhvalov | 2007-01-15 11:42:49 | Re: xml type and encodings |