From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | maybe buggy implementation of NO INDENT in xmlserialize |
Date: | 2024-08-26 05:32:53 |
Message-ID: | CAFj8pRAhZqN=WzNHKNid-6usE_qnuwbBfGrq8+pS644zEURPBA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi
I checked our implementation of xmlserialize, and it looks like there are
few issues.
1. It doesn't conform to SQL/XML - there is some overlap with the proposed
CANONICAL flag, but not full.
2. There is significantly different behaviour of NO INDENT on Oracle and
other db, that implements it. It really removes indentation from XML.
3. Oracle doesn't conform SQL/XML too fully. SQL/XML knows two states
"INDENT" x "NO INDENT". Oracle has three states: indeterminate (default),
INDENT and NO INDENT. Probably, Oracle's default (INDENT or NO INDENT) is
not the same as PostgreSQL default (without change of formatting).
Has somebody an idea, what should be expected behaviour?
Regards
Pavel
From | Date | Subject | |
---|---|---|---|
Next Message | Bharath Rupireddy | 2024-08-26 05:39:28 | Re: Introduce new multi insert Table AM and improve performance of various SQL commands with it for Heap AM |
Previous Message | Michael Paquier | 2024-08-26 04:56:40 | Re: Flush pgstats file during checkpoints |