Lists Home |
Date Index |
- From: email@example.com
- To: firstname.lastname@example.org
- Date: Wed, 21 Oct 1998 12:03:34 -0400
Two points re. translating from relational tables to XML and back.
1. The example seems reasonable but the fun really starts when you want to
represent 2 or more joined tables as an XML document. In general,
you want to map a SQL view into a XML document and if you have more
than 1 table in the view its not always clear how to structure the
2. Omitting a value is *not* the right way to represent a NULL value.
SQL distinguishes between these 2 cases. A string column can have an
empty string as a value or its value can be NULL. In DCD we recommend
that you use a special attribute to represent that the value is NULL.
image moved to "Michael Kay" <M.H.Kay@eng.icl.co.uk>
file: 10/21/98 11:28 AM
Please respond to "Michael Kay" <M.H.Kay@eng.icl.co.uk>
cc: (bcc: Ashok Malhotra/Watson/IBM)
Subject: Re: XML representation of a Table
> I just wrote an application which creates XML file from the table. All
>hava to do is to to give the table name and it will generate the XML. My
>Question, i just wanted to know, whether the XML generated is correct.
Sounds a useful application, I'd like to know more about it (especially if
you can do the reverse as well!). You can check whether the XML is
(i.e. valid and well-formed) by putting it through any xml parser, I think
xp is one of the strictest. Some test cases you need to check are your
handling of non-ASCII characters and special characters such as "<" in your
data. You also need to consider whether CR/LF characters in your data are
significant: XML treats CR=LF=CRLF which may not be what you want.
One observation, in your DTD all the columns of the table are declared
mandatory, this gives you no way of handling null values (the obvious
representation of a null value is to omit the relevant element).
Another issue you may need to address is that not every SQL table and
identifier is a valid XML name. For example, SQL identifiers can contain
You will also have to think about how to encode binary (blob) fields.
For large tables your representation is very inefficient in space terms.
Often we don't worry about this in XML work, but relational tables can
gigabytes in size even without all these tags. An alternative I would
consider for large tables is:
<COL NAME="ACTION_ID"/><COL NAME="ACTION_DESC"/> etc
I don't think the gurus would recommend using empty elements as separators
like this, but it is a perfectly legitimate use of XML.
Finally, a transfer format for relational tables also needs to be able to
represent the metadata; my example heads in this direction.
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)