|
Version
|
Date
|
Changes
|
| 3.64 |
08/02/07 |
- Added support for a new XML datatype in DB2 Version 9;
- AAdded support for IBM DB2 v. 9 PureXML technology with a new XML
datatype allowing data access via SQL or XQuery statements;
- Fixed a problem causing the driver to throw an
HITDB2EOS exception.
|
| 3.63 |
05/31/07 |
- Added a new connection option "security_mechanism" to allow an encrypted
user and password;
- Fixed conversion issues for codepage 1200 (UTF16);
- Fixed an issue with batch update on mainframes when autocommit is off;
- Fixed an issue with batch update when "defer_pps" is on.
|
| 3.61 |
01/30/07 |
- Fixed a very rare synchronization issue with character conversion operations;
- Fixed a problem where 0 is incorrectly returned as an update count when
there is a LOB parameter;
- Fixed an issue with autocommit when a SELECT is a last statement in the
connection to be closed;
- Modified the driver to recognize DB2 Version 9;
- Improved performance of batch operations;
- Changed the default value of the option "continue_execute_batch" to YES;
- Added support for Statement.Cancel for the database versions that support
Interruption Request.
|
| 3.59 |
04/10/06 |
- Fixed a problem which caused the driver to throw an exception when trying to
recover a previously interrupted XA transaction;
- Fixed a problem which caused the driver to retrieve output parameters
incorrectly under the following condition: when calling stored procedures
from DB2 V8 on z/OS with the database default CCSID of 1208, and a driver
connection CCSID of 37.
|
| 3.57 |
02/06/06 |
- Fixed a synchronization problem that occurred when calling commit() or
rollback() from a thread while there were statements being executed on the
same connection in other threads.
|
| 3.56 |
12/30/05 |
- Fixed a problem with a truncated warning when calling stored procedures
with a returned parameter;
- Fixed a problem with retrieving a long result set that includes LOB
columns on DB2 V6 and V7 of DB2 running on mainframes.
|
| 3.55 |
10/21/05 |
- Modified Clob.getSubString to return "" instead of throwing an exception
when a clob length of 0 is passed;
- Modified Blob.getBytes to return new byte[0] instead of throwing an
exception when a blob length of 0 is passed;
- Made a change to return new b[0] instead of null when a VARBINARY
column's length is 0;
- Added connection option "stream_as_clob" to treat a stream as a clob when
auto conversion is off;
- Modified setString to use the actual string if Time & Timestamp
conversion fail in order to allow application to pass native database
format (when auto conversion is on);
- Fixed an issue with re-executing a stored procedure after a commit;
- Added a new option "query_timeout" for setting a default query timeout;
- Added "+" as an additional delimiter for specifying an alternate server list.
|
| 3.53 |
07/06/05 |
- Added class hit.db2.Db2WLSV8XADataSource for use with Weblogic and DB2 Version 8;
- Fixed a problem where a var/char stored procedure output parameter got treated
as BINARY when default database CCSID was different from the parameter's CCSID;
- Created a special version of the driver to be used with Oracle's JDK 1.3
(Customers interested in this version should contact HiT Software for more
information);
- Fixed a problem that occurred when a CLOB parameter's CCSID was set to 1208;
- Fixed a problem that occurred when using DB2 UDB V8 with a prepared statement
that is reused across commits;
- Added a "reconnect_sysplex" option to enable the driver to reconnect
automatically to another SYSPLEX member when the current connection fails.
|
| 3.50 |
01/14/05 |
This version requires
a new license jar file. Contact HiT Software for the license file.
- Fixed a connection problem that occurred when connecting to older databases;
- Fixed problems with some database metadata calls against DB2 running on Solaris;
- Fixed problems with STATIC SQL and added support for STATIC SQL on V8 databases;
- Modified support for TMJOIN to allow TMJOIN to resume an ended transaction (to
support a Weblogic behavior).
|
| 3.30 |
10/07/04 |
- Added support for DB2 Version 8 running on LINUX390;
- Added support for DB2 Version 8 running on Z/OS;
- Added XA support for DB2 Version 8 on all platforms;
- Added support for CCSID 923;
- Fixed a problem in method setTransactionIsolation() when the connection is an XA connection;
- Fixed a problem with result sets containing LOBs from stored procedures;
- Fixed a problem with LOB output parameters from stored procedures;
- Fixed a problem with UNICODE datatype columns on DB2 on OS/390;
- Fixed a problem with retrieving parameters from stored procedures that have more
than 84 parameters.
|
| 3.21 |
06/01/04 |
- fixed a problem with setXXX() for BIGINT datatype when auto_type_conversion=yes;
- fixed a problem with re-execution of a prepared statement on DB2 Version 8.1;
- fixed some problems with database metadata functions on DB2 Version 8.1 on AIX;
- provided support for DB2 Version 8.1 with 64-bit on AIX;
- changed getXXX methods in ParameterMetaData to return null instead
of "" if auto_type_conversion is off.
|
| 3.20 |
05/07/04 |
- SSL libraries are now FIPS-validated;
- SSL classes have been removed from the main driver's jar file and will be
loaded dynamically when used;
- Fixed a bug when setFetchSize(0) is called;
- Added support for Polish CCSID 912;
- Allowed prepared statements to be re-used across XA transactions;
- Added the connection option "job_name" that can be used to specify the job
name/ID for JDBC connections. If not specified, the default value "DB2JDBC"
is used;
- Added the option "alternate_servers" that can be used to specify a list of
alternate servers to be used when the driver cannot connect to the primary
server;
- Made modifications to further enhance overall database queries performance.
|
| 3.11 |
12/18/03 |
- Added: The connection option "append_create_table"
that can be used to tell the driver to append the specified
value to CREATE TABLE statements that do not have an IN
DATABASE clause;
- Fixed: Minor fixes to database metadata methods;
- Fixed: The problem of incorrect error-code returned when
a bad SQL statement is executed;
- Enhanced: Extend connection URL syntax to allow the rdbname
to be specified without using the "rdbname" option.
Example: "jdbc:db2://mysrv:446/S390LOC" can be
specified;
- Added: Support for XA calls on a transaction using a resource
manager that is not the one the transaction was started
on (this is done to work around a problem with Weblogic
Server 6.1).
|
| 3.10 |
06/06/03 |
|
| 2.80 |
01/21/03 |
- Added support for DB2 UDB Version 8.1 on Windows, Linux,
UNIX. Also, added support for stored procedures and LOB
data types to this new database version;
- Enhanced JDBC trace output and added a new connection
option named trace_level that can be used to specify the
level of information written to the trace file. The default
level is 5 and will include all information. If 0 is specified,
no information will be written to the trace;
- Added a new connection option named remove_sql_white_spaces
that can be used to tell the driver to remove white spaces
such as tabs and new lines from SQL statements before sending
them to the database. By default, the driver does not remove
any white spaces from the SQL statements;
- Added support for remote monitoring of connection activities
and the execution of statements. A new java utility application,
hit.db2.RemoteMonitor, is used to monitor when connections
are created and closed. The new connection option remote_monitor_address
is used to enable remote monitoring and to specify the IP
address and port number where the remote monitoring application
is running and listening. When a connection is created or
closed, the driver sends a message to the remote monitoring
application to identify the connection and update the total
number of connections;
- Added a new connection option named current_sqlid that
can be used to set the current SQL ID for the connection.
When this option is specified, the driver internally executes
a SET CURRENT SQLID command with the specified value;
- Added a new connection option name current_function_path
that can be used to set the schema path list for calling
functions and stored procedures. When this option is specified,
the driver internally executes a SET CURRENT FUNCTION PATH
command with the specified list;
- Fixed a bug when setting a decimal column, on UDB DB2
databases only, with the value 0.00 using setBigDecimal();
- Added support for Arabic, ccsid value 420.
|
| 2.71 |
09/27/02 |
- Fixed a bug that caused an error when calling stored procedures
that don't have parameters on DB2 6.0 and higher;
- Fixed a bug in method setLong() that truncated the parameter
value to int;
- Fixed a bug introduced in 2.70 that caused a cursor error
under some conditions.
|
| 2.70 |
09/10/02 |
- Added a new connection option named defer_pps that
can be used to defer the compilation of prepared statements
until the statements are executed. Turning on this option
may improve driver performance under some network conditions
as the network flows of a statement's preparation and execution
are combined into one. This option is ignored if the auto_type_conversion
option is set to yes;
- Database data type names are now returned as standard
names instead of DRDA data type names;
- Fixed a bug that had previously limited applications from
calling more than 10 stored procedures simultaneously in
one connection;
- Both methods, executeQuery() and executeUpdate(),
of the CallableStatement interface can now invoked
even if a result set is returned by the stored procedure;
- Added a new connection option named auto_create_packages
that can be used to tell the driver not to check and create
packages automatically. By default, the driver now checks
for the existence of the packages that it uses and creates
them if they don't exist. The driver does the check by executing
a simple DECLARE statement and examining the returned SQL
code. However, this check always logs an error message with
the database. Setting auto_create_packages to no
now tells the driver to assume that packages have been created
by the driver before and not to check when the connection
is made. We recommend that this option be set to no
after the application has been tested;
- Provided a new configuration class that users can modify
and compile to customize default connection setting values
for their own system;
- Added a new connection option named config_class
that can be used to specify a compiled Java class which
contains custom default connection setting values;
- Added support for recording, binding and using DB2 Static
SQL statements. The new option record_static_sql
is used to turn on Static SQL recording. A new java utility
application hit.db2.BindStaticSql is used for binding
the recorded Static SQL statements to the database. The
new option use_static_sql is used to specify the
java class that contains the recorded and bound Static SQL
statements;
- Users can now specify the location and name of the binding
files used by hit.jndi.jdbccontext.JDBCNameContextFactory
by defining a full filepath for the hit.jndi.jdbccontext.binding_file
property
|
| 2.61 |
05/21/02 |
- Added a work-around for a conversion problem caused by
IBM's JDK 1.2 when calling setFloat();
- Added a new connection option named "application_server"
that can be used to specify the type of application server
the driver is being used from. This option is required when
using IBM WebSphere Application Server Version 4.0.2 or
higher and hit.db2.Db2XADataSource. The value is "WAS".
For example: application_server=WAS. Please see the online
help section that describes how to configure our driver
with WebSphere Application Server for more information.
|
| 2.60 |
03/29/02 |
- Implemented XA support for DB2 Version 6.1 or higher on
OS/390.
|
|
2.52
|
01/10/02
|
- Added a "continue_execute_batch" option. The
default behavior when an exception is encountered while
executing a batch statement is to stop the execution. With
the "continue_execute_batch" option set to "yes",
the driver will continue executing all statements and return
any failed status as specified in the JDBC 3.0 specs;
- Allowed BLOB columns to be set with setBinaryStream()
and setBytes() methods;
- Allowed CLOB columns to be set with SetCharacterStream()
and setString() methods;
- Fixed a bug where 83 columns were selected;
- Allowed statements to execute after rollback is called;
- Allowed statements to execute when transaction isolation
level is changed;
- Now retrieves correct cursor names for result sets returned
by stored procedures;
- Fixed a bug where some database warnings were treated
as exceptions;
- Fixed a bug where calling Statement.close() after rollback()
raised exceptions;
- Fixed a bug in getProcedures() and getProcedureColumn()
for 390 and DB2 version 6 and up;
- Fixed getLong() so that some data will not be truncated;
- Metadata schema, calatog and table column names are now
returned as empty strings instead of nulls;
- Fixed DECIMAL and ZONE datatype conversion problem when
running on JVMs that use non-standard encoding such as OS390.
|
|
2.51
|
05/14/01
|
- This version of the driver will require a new license
key which will be provided to all existing customers with
maintenance and support contract - simply contact us to
get your new license key.
- Starting from this version, the JDBC driver will be distributed
in a jar file and the license key will also be included
in a separate jar file. The CLASSPATH must include these
two jar files.
- Fix the problem where EXECUTE privilege was not granted
to a newly created package when auto commit is disabled.
- Trailing spaces and semicolons are removed from SQL statements.
- Fix problems with calling store procedures on non OS/390
platforms (However, because these platforms - including
Windows - do not provide complete support for calling store
procedures via DRDA - the protocol that the HiT driver uses
- we recommend our customers to contact us if they wish
to do this).
- Add support for DatabaseMedataData's getImportedKeys,
getExportedKey and getCrossReference on Windows platforms.
- Fix a problem when valid licenses were not recognized
when running under IBM built JVMs.
- Fix a problem introduced in version 2.50 that gave a bind
error when connecting to Solaris platform
|
|
2.50
|
03/22/01 |
- Added support for JDBC 2.0 Optional Package DataSource
interface, including a connection pooling implementation.
hit.db2.Db2DataSource provides normal connection objects.
hit.db2.Db2PooledDataSource provides connection pooling
management. See sample applications in samples/DataSources
for examples of using these classes.
- Added a JNDI service provider to use with the JDBC driver.
The context factory name is hit.jndi.jdbccontext.JDBCNameContextFactory.
See sample applications in samples/DataSources for examples
of using the JNDI service provider with HiT data sources.
- Added support for LOB data types (large binary objects)
on DB2 databases that support LOB via DRDA.
- Fixed a rounding problem in ResultSet.getDouble() when
the data type is decimal.
|
|
2.4.2
|
08/28/00
|
- Add password change capability on databases that support
the feature.
- Return different messages for invalid user and invalid
password on databases that support the feature.
- Some performance improvement for reading from database.
- Fix a synchronization problem when driver is used with
very fast systems.
- Add support for VALUES statement.
- Add support for Japanese code pages 943 and 954.
- Fix ResultSet.getObject() problem that returned null instead
of an empty String.
- Fix a problem in some DatabaseMetaData methods when using
DB2 on LINUX.
- Fix a problem when calling store procedures on systems
with v4r4 or higher.
- Fix a connection error that was introduced by IBM on v4r5
and a patch on v4r4.
|
|
2.4.1
|
07/12/00 |
- Fixed a code page conversion problem.
|
|
2.4.0
|
06/01/00 |
- Added support for SilverStream Application Server 3.0
|
|
2.3.0
|
03/28/00
|
- Added support for double-byte character sets
|
| 2.2.2 |
|
- Fixed a setDate() bug where dates with a year values less
than 1000 caused an error
- Added code pages 1027 (Japanese Latin Host SBCS) and 290
(Japanese Katakana Host SBCS)
|
| 2.2.1 |
02/25/00 |
- Fixed a floating point conversion bug in setFloat() and
setDouble() which caused some large values to be written
to the database incorrectly
- Write operating systems and Java environment information
into the trace if it’s to be generated
|
| 2.2.0 |
12/10/99 |
- Implemented JDBC 2.0 Core API
- Added support for connecting to DB2/400 via SSL Server
for data encryption and server authentication
- Added support to enable SilverStream Application Server
to access DB2 data using HiT JDBC/DB2
- Cryptography classes no longer available-replaced by HiT
SSL Server
- Added “trace_file” connection option. This option
can be used by applications to direct detailed JDBC trace
into a file
- Added “catalog_qualifier” connection option.
This option is used to override the default catalog used
to retrieve database metadata (the default catalog is SYSTEM
or SYSIBM depending on the OS)
- Added “search_schema” connection option. This
option should be used for applications that make database
metadata calls to large databases. This option is used to
limit the metadata searches to the specified schema when
a null schema was specified by an application. If this option
is not used then all schemas are searched by default
|
1.1.1
|
06/06/99
|
- Removed JDK 1.0.2 version of driver. The JDK 1.0.2 version
will still be available upon request
- Fixed problem related to maximum number of connections
reached in an applet.
- Hold cursors on commit option added called: “hold_cursor”.
This option will hold the cursor after a commit when set
to “yes”. Normally, when a commit occurs, all
cursors are closed. Some applications do not function appropriately
if cursors are closed. In such cases you use this option
to keep cursors open. For example, if “hold_cursor=yes”,
and you fetch rows from a result set, then commit, cursors
remain open so you can continue to fetch additional row
from the result set. The default value for this option is
“no”. Example url: “jdbc:db2://1.1.1.1;rdbname=FOO;hold_cursor=yes”
|
1.1.0
|
04/06/99
|
- Fixed problem with setString(n,string) method of PreparedStatement
& CallableStatement. Version 1.1.0 incorrectly required
the string parameter to have the same length
- Fixed problem where driver returned a null string instead
of an empty string for blank columns
- All SQLException exceptions are thrown with a non null
SQLState
- Added option "naming" which allows the use of
system naming convention by setting "naming=system"
in the connection options. The alternative to "naming+system"
is "naming+sql", which is the default. NOTE: If
a library name contains a period ('.'), it is still necessary
to put the library name in double quotes (ie: SELECT * FROM
"A.LIB"/AFILE)
|
| 1.0.7 |
02/12/99 |
- Fixed problem with driver hanging or misleading exception
when invalid username or password specified
- Fixed problems with driver returning a null string instead
of an empty string for blank columns
- Fixed problem with calling registerOutParameter() before
calling setXXX() methods
- Improved performance for Statement.executeUpdate() method.
|
|
1.0.6
|
02/02/99 |
- Fixed problem with methods larger than 64K causing verify
error with certain browsers (especially Netscape)
- Fixed problems with DatabaseMetaData.getColumns
|
| 1.0.5 |
01/25/99 |
|
| 1.0.4 |
01/19/99 |
- Addition of DDM parameter (CRRTKN) required for some databases
- Correction of floating point value handling
|
| 1.0.3 |
12/27/98 |
- Added Euro character to conversion tables
- Made minor changes to PreparedStatement interface
|
| 1.0.2 |
10/26/98 |
- Stored procedures with result sets are now supported
|
| 1.0.0 |
08/12/98 |
- DatabaseMetaData methods have been completed
- Added conversion tables for CCSID 277 (Norwegian
|
