[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: XML representation of a Table

• From: Pavel Velikhov <pvelikho@c...>
• To: xml-dev@i...
• Date: Wed, 21 Oct 1998 12:57:56 -0700

Michael Kay wrote:

> 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 column
> identifier is a valid XML name. For example, SQL identifiers can contain
> spaces.
>

It seems that throwing relational attributes into XML attributes overcomes both
problems - make all attributes optional, all that are missing are null.E.g.
<row action_id="A" action_desc="PASSTEST" ... />, everything that is not present
is null.
Not a space efficient representation however.

> 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 reach
> gigabytes in size even without all these tags. An alternative I would
> consider for large tables is:
>
> <TABLEDEF NAME="ACTION">
>   <COLUMNS>
>     <COL NAME="ACTION_ID"/><COL NAME="ACTION_DESC"/>  etc
>   </COLUMNS>
> </TABLEDEF>
> <TABLE NAME="ACTION">
> <ROW>A<C/>Activate<C/>A<C/>PASSTEST<C/>1998-02-23 09:44:00.000</ROW>
> <ROW>...</ROW>
> </TABLE>
>
> I don't think the gurus would recommend using empty elements as separators
> like this, but it is a perfectly legitimate use of XML.
>

My subjective view is that with current XML tools (msxml parser for example) its
a lot easier to process XML objects that store data in attributes rather than in
subobjects. Empty elements and PCDATA interleaved makes life complicated for no
good reason. Plus you have to care for order when creating tables in XML, instead
of just setting attributes in an arbitrary fashion.

> Finally, a transfer format for relational tables also needs to be able to
> represent the metadata; my example heads in this direction.
>

Is there a standard under development for such a thing? I.e. full scale transfer
format for relational tables in XML?

> Regards,
> Mike Kay

Thanks
Pavel Velikhov


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• References:
  • Re: XML representation of a Table
    • From: "Michael Kay" <M.H.Kay@e...>

• Prev by Date: Re: XML representation of a Table
• Next by Date: Re: DTD Question
• Previous by thread: Re: XML representation of a Table
• Next by thread: Re: XML representation of a Table
• Index(es):
  • Date
  • Thread