From: | "Nikolay Samokhvalov" <samokhvalov(at)gmail(dot)com> |
---|---|
To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: xml type and encodings |
Date: | 2007-01-15 11:42:49 |
Message-ID: | e431ff4c0701150342w88e7eaex35c39048dc62bf95@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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?
--
Best regards,
Nikolay
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2007-01-15 13:29:57 | Re: xml type and encodings |
Previous Message | ITAGAKI Takahiro | 2007-01-15 09:53:49 | Re: O_DIRECT support for Windows |