No. Throwing threads at the Bridge is generally always a bad idea. ODBC
drivers are not guarenteed to be thread-safe to begin with.
Statements/ResultSets are considered "active" from the time they are created
until they are closed; not just when you are making method calls on them.
Karl.
-----Original Message-----
From: JustinMacCarthy [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 04, 2001 11:22 AM
To: JRun-Talk
Subject: RE: JDBC Drivers +
Thanks Karl , that was my conclusion as well. The SQL IS only allowing one
statements (according to getMaxactiveStatements), Access allowed 64. So I
created a vector :-)
This leads to another Question though, is it possible to wait using
Java-Odbc until the statement is not active any more before continuing with
the next getColumns statement?
I even tried code like this :
getColumns()
while( continue )
{
try
{
wait
getColumns;
continue = 0
}
catch (SQLError using getColumns())
{
continue = 1 ;
}
}
...... but it just timed out all the time.
I can work around it but I guess I'll like trying to figure out whats
happening under the hood :-)
Thanks for your help/ thoughts ....
Justin
>-----Original Message-----
>From: Karl Moss [mailto:[EMAIL PROTECTED]]
Maybe SQLServer is
>doing some special statement processing/caching when using metadata that
>precludes you from having multiple active statements - I just don't know
>what the ODBC driver is doing under the covers.
>
>The generic way to program for this case is to build an
>array/Vector/Collection of the table names up front, and then process the
>column names for each table in a separate loop.
>
>Hope this helps,
>
>Karl.
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
