Subject Re: JBuilder DataSet Components and Firebird
Author Roman Rokytskyy <rrokytskyy@yahoo.co.uk>
Hi,

> However, we ran across several problems with interclient and about
> two weeks ago we though to try out the new driver and it seemd to
> solve a lot of problems, but it did brake the interaction with the
> JBuilder components (We were not able to save records using the JB
> swing classes, we got the same error message which someone posted
> earlier). So we got the latest CVS source and tried the latest
> driver and then we encountered the SQLDA exception (see my previous
> post).

Your problem with XSQLDA version seems to be related to database
server v.0.9.4. Firebird 1.0 was released a long time ago, and it
fixed a lot of bugs in 0.9.4. So, I would recommend to upgrade your
database server.

> How much work would it be to implement those missing features
> (guess)? And how much experience would one need to do such thing?
> Maybe I could free up some time to do this, but I'm affraid it
> might take a lot of time to get into the internals of the driver
> especially because I don't know anything about the specs and not
> much about how application servers such as JBoss use the Driver.

If you want a same workaround as InterClient has, you can patch your
sources. Look into the file client-
java/src/main/org/firebirdsql/jdbc/FBPreparedStatement.java, in
method setObject(int, Object, int, int) you comment out throwing an
exception and change it like this:

public void setObject(int colIndex, Object value, int sqlType, int
scale) throws SQLException {
// this is a workaround, we ignore sqlType and scale
// hoping that nothing bad happens

setObject(colIndex, value);
}

I do not think that we will add this code to the CVS version, because
ignoring some parameters is not very nice, but you can keep your CVS
snapshot and synchronize with main tree. Since we do not plan to
change this method, there should be no conflicts, but even if they
are you can patch code from the CVS.

In general, it would be great if somebody can provide a list
unimplemented methods that are used by JBuilder components and post
them in a bug tracker and here. This will help us prioritize features.

Best regards,
Roman Rokytskyy