This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Xalan ODBC extension - implementation
- From: Curtis Burisch <burisch at clara dot co dot uk>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Tue, 22 Jan 2002 11:57:46 +0000
- Subject: [xsl] Xalan ODBC extension - implementation
- Reply-to: xsl-list at lists dot mulberrytech dot com
Hi,
At my company are implementing an extension function to Xalan which
queries an ODBC database. An SQL string is passed in, and the result
set is returned. We are still in the process of defining how the result
set will be returned.
When one row, one column (i.e. a single value) is returned, there is no
problem. However, when multiple rows & columns are returned, I am
unsure how to structure the data returned, or if indeed this is the
right way to be going about the problem.
Our plan at the moment is to return an xml fragment, something like:
<Record>
<Field name="fred">test1</Field>
<Field name="joe">test2</Field>
</Record>
<Record>
<Field name="fred">test3</Field>
<Field name="joe">test4</Field>
</Record>
Now, obviously this would be returned as a string and won't be parsed
into a tree fragment, and thus can't be interpreted by Xalan -- is
there any way to do it?
It's also highly possible that we're re-inventing the wheel. Has
anybody heard of or used an extension which would meet our requirements?
Many thanks for your time!
Best regards,
Curtis Burisch.
--
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list