X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 41FC9D1B444 for ; Fri, 9 Jan 2004 19:22:55 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 67200-02 for ; Fri, 9 Jan 2004 15:22:24 -0400 (AST) Received: from mail.hive.nj2.inquent.com (mc.carriermail.com [205.178.180.9]) by svr1.postgresql.org (Postfix) with SMTP id BFC43D1B47D for ; Fri, 9 Jan 2004 15:22:07 -0400 (AST) Received: (qmail 739 invoked from network); 9 Jan 2004 19:22:33 -0000 Received: from unknown (HELO ?10.0.2.18?) (216.208.117.7) by 205.178.180.9 with SMTP; 9 Jan 2004 19:22:33 -0000 Subject: Re: Encoding problems in PostgreSQL with XML data From: Rod Taylor To: Peter Eisentraut Cc: PostgreSQL Development In-Reply-To: <200401091946.01930.peter_e@gmx.net> References: <200401091946.01930.peter_e@gmx.net> Content-Type: text/plain Message-Id: <1073676109.1521.18.camel@jester> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Fri, 09 Jan 2004 14:21:50 -0500 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/213 X-Sequence-Number: 48937 > Rewriting the 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.