Request a Demo
Home   >   mailing lists

Re: BUG #16277: xmlelement allows invalid XML characters when XMLversion is set to 1.0 - Mailing list pgsql-bugs

From Andreas Lennartsson
Subject Re: BUG #16277: xmlelement allows invalid XML characters when XMLversion is set to 1.0
Date
Msg-id CAOWD6R_V77BhLpBKW0GYRd6XOe6WEBTkZEj4FBMBhGH6JpV_0Q@mail.gmail.com
Whole thread Raw
In response to Re: BUG #16277: xmlelement allows invalid XML characters when XML version is set to 1.0  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tree view
>On what grounds do you call it invalid?
Based on the valid control characters for XML 1.0 https://en.wikipedia.org/wiki/Valid_characters_in_XML

>What other behavior would you expect?
I would expect valid XML 1.0 to be generated on success.
If that is not possible I would expect an error.

Thanks,

Andreas 

On Tue, Feb 25, 2020 at 2:59 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
PG Bug reporting form <noreply@postgresql.org> writes:
> The following example:
> SELECT
>   xmlroot (
>      xmlelement (name "test", CHR(26))
>   , version '1.0'
>   )

> Produces xml with the invalid ASCII character 26.

On what grounds do you call it invalid?  What other behavior
would you expect?

                        regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: planner weirdness: a join uses nestloop with checking condition when there are two subplan-or-hashed subqueries
Next
From: Tom Lane
Date:
Subject: Re: BUG #16277: xmlelement allows invalid XML characters when XML version is set to 1.0