I am trying to implement a better method than I already have to document
database schemas with XML, and use XSLT to both generate database DDL
statements (CREATE TABLE, etc) and to transform to HTML for documentation
purposes. In particular I want XSLT to transform to HTML so that my XML
documents can be "live", doing the transform in the browser.
In the new system a very short XML document looks like:
<database>
<table id="PROVIDER">
<field name="KEY" type="decimal" precision="9" scale="0"/>
...
<primary-key id="PKPROVIDER " fields="KEY"/>
</table>
<table id="PERSON">
<field name="PROVIDER"/>
<field name="KEY" type="decimal" precision="9" scale="0"/>
...
<primary-key id="PKPERSON" fields="PROVIDE R KEY"/>
<foreign-key id="FKPERSON" fields="PROVIDE R" foreign-table="PROVIDER "
on-delete="cascade " on-update="restric t"/>
</table>
</database>
Short description would be:
PROVIDER - a table
PROVIDER.KEY decimal(9,0) (is primary key, so not-null and unique).
Primary key is PROVIDER.KEY
PERSON - a table
PERSON.PROVIDER is foreign key to PROVIDER.KEY, so is same data type.
PERSON.KEY decimal(9,0) is unique number within provider.
Primary key is PERSON.PROVIDER and PERSON.KEY
Foreign key to the PROVIDER table where PERSON.PROVIDER = PROVIDER.KEY
Note that PERSON.PROVIDER doesn't have any type,etc attributes. Since
PERSON.PROVIDER is actually a foreign key to the PROVIDER.KEY field, the
two fields need to have the same data type, and when generating DDL, etc
the data type should be looked up from the field that this foreign field
references. Therefore PERSON.PROVIDER 's data type should be listed as the
same as PROVIDER.KEY's type,precision, etc. A "gotcha" is that
PERSON.PROVIDER could possibly be listed in more than one foreign-key
element, so I'd have to only follow the first one found.
I'm trying to write a template (mode="datatype ") for a field node which
outputs the actual type,precision, length,etc values for a field. In the
case of PROVIDER.KEY that's easy, because it is explicitly defined by the
attributes for the node. But for PERSON.PROVIDER I can't figure it out. So
far my template looks like:
<xsl:template match="field" mode="datatype" >
<xsl:choose>
<!-- If type is present, go ahead with the data type -->
<xsl:when test="@type">
<xsl:choose>
<!-- If length present, write out type(length) -->
<xsl:when test="@length"> <xsl:value-of
select="@type"/>(<xsl:value-of select="@length "/>)</xsl:when>
<xsl:when test="@precisio n">
<!-- If precision is present... -->
<xsl:choose>
<!-- If scale is also present, write out type(precision, scale)
-->
<xsl:when test="@scale">< xsl:value-of
select="@type"/>(<xsl:value-of select="@precis ion"/>,<xsl:value-of
select="@scale"/>)</xsl:when>
<!-- Otherwise write out type(precision) -->
<xsl:otherwise> <xsl:value-of select="@type"/>(<xsl:value-of
select="@precis ion"/>)</xsl:otherwise>
</xsl:choose>
</xsl:when>
<!-- No length,precisio n,scale - write out type -->
<xsl:otherwise> <xsl:value-of select="@type"/></xsl:otherwise>
</xsl:choose>
</xsl:when>
<!-- Otherwise, assume it is a foreign key and use the foreign field
instead -->
<xsl:otherwis e>
????????????
</xsl:otherwise>
</xsl:choose>
</xsl:template>
Any help appreciated.
