JayBird 1.5.2

Contains fixes to some reported issues with v.1.5.1.

• There should be no more “invalid statement handles”
• Result sets should be correctly released when using the connection pool.
• Some more fixes should remove the “cannot start transaction, local transaction active”. A
• It is now possible to specify both isc_dpb_lc_ctype and charSet encodings. In this case lc_ctype is passed to the database, charSet is used to convert bytes to characters. The most useful case is when lc_ctype=NONE. Previously the driver used the default JVM encoding to convert bytes into strings. Now you can enforce the encoding you like and do not need to depend on the regional settings of the host OS.

Attempts to build it with JDK 1.5, were not successful. The build system cannot run with 1.5 (the target=”1.2” part in build.xml and the used version of Ant does not understand 1.5), and at least the JNDI code from the pool does not compile due to use of generics in the JNDI API.

Most likely one can build driver by using the “compatibility” mode of the compiler, but the build system must be fixed (probably requires upgrade of Ant). I think we would need to split the code bases the same way I did it for JDK 1.3 and JDK 1.4. Are there any volunteers for this task?