I will look into the error, on no rows returned. I just ran into this problem myself this week so it is at the top of my list.
As for the connections, it is possible that the connection is dropped for each transformations. If you are using the default connection pool (by specifying connection information in the XSL file) I believe that we changed the "Min" connections from 5 to 1, so you will see the build connection / drop connection behavior. In a repetitive / production environment the SQL extension is designed to have externally controlled connection pools. Now you don't have to write / acquire connection pool code, the code in the Xalan lib is finn. You just need to establish the pool outside the Xalan code, i.e. in you application. I would look at the ext-connection sample code to see how it is accomplished. Once you do that, you have much more control over connection usage. Regards John G Phil Friedman wrote: > I'm upgrading from XALAN 2.0.1 to 2.3.1, if I don't disable streaming w/ > > <xsl:value-of select="sql:disableStreamingMode($DbCon)"/> > > in a query that returns no rows I get "SQL Error Fetching next row [null]", > such as: > > file:///C:/362Taxi/362ClnChr2_3_1s.bat.xsl; Line 40; Column 44; select * from aldr >where 1=0 > file:///C:/362Taxi/362ClnChr2_3_1s.bat.xsl; Line 42; Column 20; Error in Query > <?xml version="1.0" encoding="UTF-8"?> > <ext-error> > <message>SQL Error Fetching next row [null]</message> > > This query has predictably not rows (1=0), but other queries may or may > not return rows. > > Regards, Philip Friedman -- Terralink Software Systems -- 207-772-6500 > x101
