[PATCH] empty xml values
While looking into this report
/messages/by-id/CF48CCFB.65A9D%25tim.kane@gmail.com I
noticed that we don't accept empty values as xml "content" values, even
though this should apparently be allowed by the spec. Attached is a
patch to fix it (which needs updates to xml_1.out, which I omit here for
simplicity).
Attachments:
xml-empty.patchtext/x-patch; name=xml-empty.patchDownload+35-0
While looking into this report
/messages/by-id/CF48CCFB.65A9D%25tim.kane@gmail.com I
noticed that we don't accept empty values as xml "content" values, even
though this should apparently be allowed by the spec. Attached is a
patch to fix it (which needs updates to xml_1.out, which I omit here for
simplicity).
The patch works, albeit must be applied with --ignore-whitespace. Attached
the patch + xml_1.out updates.
I'm marking this ready for commit
--
Ali Akbar
Attachments:
xml-empty-add-xml_1.patchtext/x-patch; charset=US-ASCII; name=xml-empty-add-xml_1.patchDownload+56-5
On 8/30/14 12:43 PM, Ali Akbar wrote:
While looking into this report
/messages/by-id/CF48CCFB.65A9D%25tim.kane@gmail.com I
noticed that we don't accept empty values as xml "content" values, even
though this should apparently be allowed by the spec. Attached is a
patch to fix it (which needs updates to xml_1.out, which I omit here for
simplicity).The patch works, albeit must be applied with --ignore-whitespace.
Attached the patch + xml_1.out updates.I'm marking this ready for commit
Committed, thanks.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers