Re: Fix XML handling with DOCTYPE
Chapman Flack <chap@anastigmatix.net>
From: Chapman Flack <chap@anastigmatix.net>
To: Ryan Lambert <ryan@rustprooflabs.com>, pgsql-hackers@lists.postgresql.org
Cc: Pavel Stehule <pavel.stehule@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2019-03-27T05:53:20Z
Lists: pgsql-hackers
On 03/26/19 21:39, Ryan Lambert wrote: > I can't verify technical accuracy for many of the details (nuances between > XPath 1.0, et. al), but overall my experience with the XML functionality > lines up with what has been documented here. By the way, in case it's buried too far back in the email thread now, much of the early drafting for this happened on the wiki page https://wiki.postgresql.org/wiki/PostgreSQL_vs_SQL/XML_Standards which includes a lot of reference links, including a nice paper by Andrew Eisenberg and Jim Melton that introduced the major changes from the SQL:2003 to :2006 editions of SQL/XML. Cheers, -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