Re: Fix XML handling with DOCTYPE
Chapman Flack <chap@anastigmatix.net>
From: Chapman Flack <chap@anastigmatix.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Ryan Lambert <ryan@rustprooflabs.com>, pgsql-hackers@postgresql.org
Date: 2019-03-23T23:07:21Z
Lists: pgsql-hackers
On 03/23/19 18:22, Tom Lane wrote: >> Out of curiosity, what further processing would you expect libxml to do? > > Hm, I'd have thought it'd try to parse the arguments to some extent, > but maybe not. Does everybody reimplement attribute parsing for > themselves when using PIs? Yeah, the content of a PI (whatever's after the target name) is left all to be defined by whatever XML-using application might care about that PI. It could have an attribute=value syntax inspired by XML elements, or some other form entirely, but there'd just better not be any ?> in it. Regards, -Chap
Commits
-
Improve documentation about our XML functionality
- 728c49779ba8 11.6 landed
- 603a28b44973 10.11 landed
-
Improve documentation about our XML functionality.
- 12d46ac392d0 12.0 landed
-
Doc: clarify that REASSIGN OWNED doesn't handle default privileges.
- 50973687f185 9.6.13 cited
- 24df8662e4a4 11.3 cited
-
Suppress Append and MergeAppend plan nodes that have a single child.
- 8edd0e79460b 12.0 cited
-
Accept XML documents when xmloption = content, as required by SQL:2006+.
- 8d1dadb25bb5 12.0 landed
- da45927cef78 9.5.17 landed
- d7cfd5ee4591 9.6.13 landed
- 849f87a1c334 11.3 landed
- 78f84fe0f478 9.4.22 landed
- 754ffcd42006 10.8 landed
-
Ensure xmloption = content while restoring pg_dump output.
- 4870dce37fab 12.0 landed
- 8ba485422933 9.4.22 landed
- 08d8cfe3cfd6 9.5.17 landed
- de922529fe62 10.8 landed
- 7c89f350f109 11.3 landed
- 687acb598308 9.6.13 landed