Well I need some informations from a database(small part) and some from
XML-Files. If all data comes from a database I'd agree with you. Still
when having data from different sources like I have I think I've the
following possibilities:
1) Using axkit:-URIs => XSP->DBI->XML
2) Using xincludes
3) Embedd my SQL-Queries into XSL with a construct something like this:
--------------------------8<--------------------------
<xsl:value-of select="document( 'dbisql:/SELECT_*_FROM_foo' )/test"/>
--------------------------8<--------------------------
And there's one more thing I think would really by a cool thing. You
could learn XSL to query Databases using Class-DBI:
I think of something like this:
--------------------------8<--------------------------
<xsl:for-each select="document('classdbi:foo')">
FOO_COL_1: <xsl:value-of select="foo_col1"/>
<xsl:for-each select="document( 'classdbi:bar', . )">
BAR_COL_1: <xsl:value-of select="bar_col1">
BAR_COL_2: <xsl:value-of select="bar_col2">
</xsl:for-each>
</xsl:for-each>
--------------------------8<--------------------------
I know this is just a weird idea, and it does not work the way I
outlined above because when using callbacks I didn't get the
context-node passed into my callback, ... .
Tom
Am Do, 2003-08-28 um 12.46 schrieb Robin Berjon:
> But does it need to happen as a stylesheet? I would think that a simple
> Provider, using XML::Generator::DBI and a simple way to pick the simple connect
> based on the URI might suffice?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
