| From: | Andreas Lennartsson <andreas(at)apkudo(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16277: xmlelement allows invalid XML characters when XML version is set to 1.0 |
| Date: | 2020-02-25 21:14:13 |
| Message-ID: | CAOWD6R_V77BhLpBKW0GYRd6XOe6WEBTkZEj4FBMBhGH6JpV_0Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
>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(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> PG Bug reporting form <noreply(at)postgresql(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-02-25 22:00:14 | Re: BUG #16277: xmlelement allows invalid XML characters when XML version is set to 1.0 |
| Previous Message | Tom Lane | 2020-02-25 20:34:28 | Re: planner weirdness: a join uses nestloop with checking condition when there are two subplan-or-hashed subqueries |