On 7/4/06, Phillip B Oldham <phillip(_dot_)oldham(_at_)kilo75(_dot_)com> wrote:
I'd like to ask what in your opinion is the best way to store trees in
SQL for use with XSL translation.
I think we can naturally imagine the relational database as an XML
tree, where we would see the tables, rows, and columns as elements in
the XML document.
For e.g. a list of employees (an example taken from Oracle RDBMS docs)
can be modeled as the XML structure:
<EMPLOYEES>
<ROW>
<EMPLOYEE_ID>205</EMPLOYEE_ID>
<LAST_NAME>Higgins</LAST_NAME>
<SALARY>12000</SALARY>
..<!-- other columns -->
</ROW>
... <!-- other rows -->
</EMPLOYEES>
This could be stored in the relational database as an EMPLOYEE table.
Regards,
Mukul
http://gandhimukul.tripod.com/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--