Re: Sotirng data in row versus storing the same in column

>> Three letters: XML.  

    <foo>

      <bar>this</bar>
      <mug>is</mug>
      <wump>an</wump>
      <ech>elegant</ech>
      <urp>datamodel?</urp>
      <not>NOT!</not>
     </foo>
 
    =>
       +-------+---------+------------+
       | Seq#  |   Tag   |     Value  |
       +-------+---------+------------+


       |    1  |     foo |     OPEN   |

       |    2  |     bar |     this   |

       |    3  |     mug |       is   |

       |    4  |    wump |       an   |

       |    5  |     ech |    elegant |

       |    6  |     urp | datamodel? |

       |    7  |     not |       NOT! |

       |    8  |     foo |      CLOSE |

       +-------+---------+------------+ 
 
      Don't know much about schema design,
        but at XML-One, we had a really good time.
      Don't know much about anomalies.
        Why can't my data just be free,
       to be as unstructured as the bird and the bees?
         Ooh, watch the parser bring the server to its knees!
      But I know if I could just XML
         (and these SQL troglydytes would all go to hell)
        what a wonderful world it would be! <<

I gotta use the poem in a column!

>> It also explains the resurgent interest in how to manage hierarchies in RDBMS systems. <<

I am writing a book on trees in SQL, and I am not mentioning XML at all -- it is strictly SQL models. Received on Fri May 17 2002 - 17:37:25 CDT