Every time I try to run a query remotely using DBF_JDBC30 against a DBFServer running on a Novell server, with JVM 1.3.1 and DBF_JDBC20, I get an error from the driver. Something along the lines of cannot deserialize object in com.hxtt.sql.dbf.a. Do the JDBC versions of the DBFServer and client have to match?
Updating Novell JVM to 1.4 and using DBF_JDBC30 resolved the issue.
|
>Do the JDBC versions of the DBFServer and client have to match?
Yeah. You can't use a remote DBF_JDBC20 to visit a server with DBF_JDBC30. For JVM1.3.1, DBF JDBC3.0 can be used too.
|
JDBC3.0 didn't work on the Novell server. The only one that would load was JDBC2.0, so that's the one I used. It's possible the Novell JVM wasn't fully installed or wasn't installed properly.
After upgrading to 1.4 it worked fine, so I'll just use that. Thanks!
|
|
Oh. JDK1.3.X doesn't suppor java.sql.Savepoint so that HXTT DBF JDBC3.0 does some special code works to avoid that issue. One user is using JDK1.3.1 on Novell server with JDBC3.0 . Of course, JDK1.4 is better:)
|
I don't know if it's related, but I'm using 1.5.0 on my client workstation. (which seems to work fine with 1.4 on the server)
It also appears that if I use DBFServer, SquirrelSQL can no longer retrieve recordsets in this scenario. If I use a NCP mapping with a local connection, it works fine. It may be something Squirrel is doing, because my application that does a jdbc connection appears to be working fine.
|
Both of JDK1.4 and JDK1.5 support fully JDBC3.0 so that it won't resulted issue between different client JVMs.
We will try to recur your issue with SquirrelSQL for remote connection. Maybe it's resulted by a security limitation, or other unknown issues.
|
Main
webmaster@hxtt.com