Bug #19745 | mysqldump --xml produces invalid xml | ||
---|---|---|---|
Submitted: | 11 May 2006 22:09 | Modified: | 13 Nov 2006 4:37 |
Reporter: | Torrey Hoffman | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 5.0.15 | OS: | Linux (Linux) |
Assigned to: | Iggy Galarza | CPU Architecture: | Any |
[11 May 2006 22:09]
Torrey Hoffman
[12 May 2006 13:07]
Valeriy Kravchuk
Thank you for a problem report. Please, try to repeat with a newer version, 5.0.21, and inform about the results.
[12 Jun 2006 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[27 Jun 2006 12:52]
Sergei Golubchik
I agree that the output is not well-formed xml. But I'm not sure that it should respect --hex-blobs switch. Perhaps a more xml-correct solution would be to use xml encoding for otherwise invalid bytes.
[18 Oct 2006 22:43]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/13921 ChangeSet@1.2295, 2006-10-18 18:43:51-04:00, iggy@rolltop.ignatz42.dyndns.org +3 -0 Bug#19745: mysqldump --xml produces invalid xml The mysqldump command with both the --xml and --hex-blob options will output blob data encoded as hexBinary. The proper XML datatype is xs:hexBinary. The correct XML datatype is specified be setting the xsi_type attribute equal to xs:hexBinary for each encoded element.
[13 Nov 2006 4:37]
Paul DuBois
Noted in 5.0.30 (not 5.0.29), 5.1.13 changelogs. mysqldump --xml produced invalid XML for BLOB data.
[26 Mar 2008 11:38]
George Lund
I wonder if there has been a regression because I am seeing this bug using mysqldump 5.0.33. Let me know if I should submit a new bug report, thanks...