Subject | Jaybird 1.0.1 bug with dbvis 4.0.1? |
---|---|
Author | verbguy |
Post date | 2003-11-10T23:15:23Z |
Hello,
The good people over at dbvis have released a new version (4.0.1) of
their GUI tool for database administration (http://www.dbvis.com). I
tried this with Jaybird 1.0.1, and have a problem issuing a SQL
statement such as
create table foo (i int);
which works with the prior 3.3 version.
I took this up with the product manager at dbvis, and he believes
this is a problem with the Jaybird driver's handling of multi result-
set statements, as he mentions below. I didn't see this bug on the
jaybird bug list, but I may have missed it.
....
Bill,
DbVis 4.0 introduced the capability to handle multi
result sets from a single SQL statement. This have unfortunately
revealed a couple of problems with the drivers that are available
from primarily Oracle and now also for FireBird.
In the case of Oracle it is just a matter of upgrading the driver
and the problem is solved.
Technically what this means is the following calls that
DbVis issues in the JDBC layer:
Pseudo:
PreparedStatement.execute();
loop {
PreparedStatement.getUpdateCount();
PreparedStatement.getMoreResults();
}
The two calls in the loop shall return results based on
if there are any more result to get. If not then they
shall simple cause the loop to exit. It is here the
problem is. I recommend that they check the JDBC spec
to find out how it shall work. They can also contact us
for more info.
Regards
Roger
The good people over at dbvis have released a new version (4.0.1) of
their GUI tool for database administration (http://www.dbvis.com). I
tried this with Jaybird 1.0.1, and have a problem issuing a SQL
statement such as
create table foo (i int);
which works with the prior 3.3 version.
I took this up with the product manager at dbvis, and he believes
this is a problem with the Jaybird driver's handling of multi result-
set statements, as he mentions below. I didn't see this bug on the
jaybird bug list, but I may have missed it.
....
Bill,
DbVis 4.0 introduced the capability to handle multi
result sets from a single SQL statement. This have unfortunately
revealed a couple of problems with the drivers that are available
from primarily Oracle and now also for FireBird.
In the case of Oracle it is just a matter of upgrading the driver
and the problem is solved.
Technically what this means is the following calls that
DbVis issues in the JDBC layer:
Pseudo:
PreparedStatement.execute();
loop {
PreparedStatement.getUpdateCount();
PreparedStatement.getMoreResults();
}
The two calls in the loop shall return results based on
if there are any more result to get. If not then they
shall simple cause the loop to exit. It is here the
problem is. I recommend that they check the JDBC spec
to find out how it shall work. They can also contact us
for more info.
Regards
Roger