Shooter7119 / sequel-pro

Automatically exported from code.google.com/p/sequel-pro
Other
0 stars 0 forks source link

Export to XML can produce invalid XML (bad element names) #1804

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Open/create a database that has an table (or field) name that does not pass 
for a valid XML element name. (see notes)
2. Export a table to XML (using Plain Schema)
3. The exported XML will be invalid

What is the expected output?
Either character substitution, renaming the problem field entirely (possibly 
putting the original as an attribute) or throw an error and refuse to generate 
XML (possibly an option to override).

What do you see instead?
Invalid XML file generated.

What version of Sequel Pro are you using?
1.0.2

What version of OS X are you using?
10.8.4

What version of MySQL are you connecting to on the server?
5.0.51a

Please provide any additional information below.
If you have a table/field name that is not a valid XML element name (eg. begin 
with a number) the generated XML file is invalid (will break in 
parsers/applications such as XMLTidy)

Attached file shows invalid output. The table '2table' and field '2bad4name' 
are not valid XML element names.

Original issue reported on code.google.com by vliscian...@gmail.com on 5 Sep 2013 at 7:53

Attachments: