RE: XML design of Database

Subject: RE: XML design of Database
From: "Schoedl, Andreas" <Andreas.Schoedl@xxxxxxxxxxxxxx>
Date: Wed, 31 May 2000 10:56:13 +0200


> The other problem is that XML documents don't necessarily 
> lend themselves
> directly to database representations. This is particularly true for
> documents that represent marked-up text. For example, anyone 
> designing a
> database to support the following structure:
> will have a headache handling documents like this:
> <A>
>   <B>Here's some</B>text embedded <B>in</B> the A eleme<B>n</B>t
> </A>

Sorry, I couldn't resist. I put the DTD above in Tamino and stored your

Here is what comes back when retrieving the document, query string was
simple "A", meaning "give me all documents matching root-tag = A".

This was taken from IE5. Let me remind you that Tamino's answers are
themselves well-formed xml documents. The matching documents are returned in
the <xql:result/> tag; ino:id, as you already guessed, is an internal number
every documents gets.

  <?xml version="1.0" encoding="ISO-8859-1" ?> 
- <ino:response xmlns:ino="";
- <ino:message ino:returnvalue="0">
  <ino:messageline>XQL Request processing</ino:messageline> 
- <xql:result>
- <A ino:id="1">
  <B>Here's some</B> 
  text embedded 
  the A eleme 
- <ino:cursor ino:count="1">
  <ino:first ino:href="?_XQL(1,16)=A" /> 
- <ino:message ino:returnvalue="0">
  <ino:messageline>XQL Request processed</ino:messageline> 

It gets more interesting: When retrieving with query "A/B", Tamino comes
back with:
- <xql:result>
  <B ino:id="1">Here's some</B> 
  <B ino:id="1">in</B> 
  <B ino:id="1">n</B> 


Kind regards, 


Opinions expressed herein are mine, not those of my employer or my
employer's affiliates. Software AG can not be hold liable for any comments
expressed herein.

 XSL-List info and archive:

Current Thread