[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Xalan ODBC extension - implementation

Subject: Re: Xalan ODBC extension - implementation
From: "David N Bertoni/CAM/Lotus" <david_n_bertoni@xxxxxxxxxx>
Date: Tue, 22 Jan 2002 10:33:48 -0800
lotus implementation
You should join and post your questions on the Xalan-C++ or Xalan-J user
list, as appropriate.  See:


Xalan-J already has a set of SQL extensions.  Xalan-C++ does not, but it is
possible to construct nodes to represent such fragments and return them as
the result of an extension function.


                      Curtis Burisch                                                                                                            
                      <burisch@xxxxxxxxxxx>              To:      xsl-list@xxxxxxxxxxxxxxxxxxxxxx                                               
                      Sent by:                           cc:                                                                                    
                      owner-xsl-list@xxxxxxxxxxx         Subject:  Xalan ODBC extension - implementation                                   
                      01/22/2002 03:57 AM                                                                                                       
                      Please respond to xsl-list                                                                                                


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:

<Field name="fred">test1</Field>
<Field name="joe">test2</Field>
<Field name="fred">test3</Field>
<Field name="joe">test4</Field>

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

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Current Thread


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.