From: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
---|---|
To: | "Hannu Krosing" <hannu(at)tm(dot)ee> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Encoding problems in PostgreSQL with XML data |
Date: | 2004-01-12 17:56:32 |
Message-ID: | 303E00EBDD07B943924382E153890E5434AA4F@cuthbert.rcsinc.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hannu Krosing wrote:
> IIRC, the charset transformations are done as a separate step in the
> wire protocol _before_ any parser has chance transform or not.
Yep. My point is that this is wrong. I think of XML the same way I
think of a zip file contains a text document. Postgres does not unzip a
text file to change the char encoding any more than it should parse an
XML document and change the encoding unless this is the specific intent
of the user for a specific purpose.
Validation alone does not qualify as a reason because a XML parser
(xerces) can do validation server-side without mucking with document.
Postgres need only be aware of the fact that the data is XML and should
be validated.
If postgres needs to be aware of internal document contents (for
indexing, for example), XSLT can be used for that purpose.
Regards,
Merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Sai Hertz And Control Systems | 2004-01-12 18:00:19 | Re: [HACKERS] IEEE 754 |
Previous Message | Peter Eisentraut | 2004-01-12 17:48:43 | Re: psql \d option list overloaded |