Version 2.70 (will be released soon)

New Features

• User and a password to be injected into the JDBC URL. This feature can be used by JDBC drivers allowing for user/password in the URL. For example, when dealing with Oracle DB add the user/password to be injected. The password is encrypted and is required if you specify a user. It is up to the JDBC driver to use or ignore the injected password. If a user/password are specified in the CONNECT statement like: CONNECT TO SOME-RDB USER SOME-USER USING SOME-PASSWORD

Or are extracted from server authentication entries (STRDB > #21)
Or are specified in the “Force RDB User”

• The driver will make the decision whether to ignore or to respect the URL’s user/password.

Enhancements

• Avoid Kerberos lookup for the AS400 object that is created for run mode #1.
• Select statements with Three Part Name – added support for nested SELECT and WITH statements.
  Example: with tmp as (select A from B.C.D where E = 2) select * from tmp
• Better support for VARBINARY types
• For Oracle only: in ARXD0100 and ARXB0100 formats, keep original bound variables syntax in SQL statements.

Fixes

• Handling of bound variables in ARXD0100 format (Execute bound statement that returns data format). As shown here in IBM documentation:

“SELECT INTO statement produces a result table that contains at most one row. The statement assigns the values in that row to variables.”

Example: SELECT * INTO :B,:C FROM LIB.FILE WHERE A= :E

We have here three bound variables. Returned data is written to :B and :C variables.

• Removed code that deals with LONGVARBINARY type.
• We now accurately identify cases in which input bound variables have indicator variables attached. DB-Gate does not support these indicator variables, since they are pointers.
  Example: SELECT * INTO :A ,:B FROM L1.A2 where A=:C:CNULL

Here, :CNULL is an input indicator variable that is not available to DB-Gate.

• We now ship an MSSQL driver to use with Java8.