Most of the bugs of the JDBC-driver that were reported recently are fixed.
Therefor a new version of the SAP DB's JDBC-Driver
(ftp://ftp.sap.com/pub/sapdb/bin/patch/sapdb-jdbc-bin-7.3.0.23a.jar)
and Sources
(ftp://ftp.sap.com/pub/sapdb/bin/patch/sapdb-jdbc-src-7.3.0.23a.jar)
is available now for downloading.
The new version includes the following:
List patch infos and features: 21.03.2002 16:03:42
Version: 73.00.21 to 73.00.23
--------------------------------------------------
Message Id: 1112910
Message Type: Error
Version: 73.00.21
all cursor movement methods (beforeFirst etc.) now work in sqlmode oracle
--------------------------------------------------
Message Id: 1113416
Message Type: Error
Version: 73.00.21
fixed error in UpdatableResultset when fetchsize greater than one
--------------------------------------------------
Message Id: 1113457
Message Type: Error
Version: 73.00.21
SetTransactionIsolation(Connection.TRANSACTION_NONE) does not throw an
exception. a higher Isolation level will be used.
--------------------------------------------------
Message Id: 1113458
Message Type: Error
Version: 73.00.21
A password enclosed with '"'" will now be handled case sensitive
--------------------------------------------------
Message Id: 1113475
Message Type: Error
Version: 73.00.21
handle db-name always in upper cases.
--------------------------------------------------
Message Id: 1113688
Message Type: Error
Version: 73.00.21
excuteBatch with dbprocedure will work now.
--------------------------------------------------
Message Id: 1113704
Message Type: Error
Version: 73.00.21
CallableStatement.clearParameters() clears all parameters and not only the
first one.
--------------------------------------------------
Message Id: 1113803
Message Type: Error
Version: 73.00.21
for integer columns the method getColumnClassName () returns
"java.lang.Integer" instead of "java.lang.Intger"
--------------------------------------------------
Message Id: 1113969
Message Type: Change Request
Version: 73.00.21
getUDTs and getVersionColumns return an empty ResultSet instead of a
NotImplementedException
getMaxConnections returns the correct number of max possible connection
instead of -1
--------------------------------------------------
Message Id: 1113974
Message Type: Change Request
Version: 73.00.21
Statement.executeQuery() that tries to insert a row throw a SQLException
Statement.executeUpdate() that tries to select a row from the table throw a
SQLException
Statement.setFetchSize(negative) throws a SQLException.
Statement.setMaxFieldSize() now sets the value
Statement.setMaxFieldSize(negative) throws a SQLException.
Statement.setMaxRows() now set the value.
Statement.setMaxRows(negative) now throws a SQLException
Statement.setQueryTimeout(negative) throws SQLException.
The changes will be made due to standard conformance.
The EXPLAIN command returns a resultset now.
--------------------------------------------------
Message Id: 1113975
Message Type: Change Request
Version: 73.00.21
For PreparedStatement.execute() , PreparedStatement.executeUpdate() and
PreparedStatement.executeQuery() a SQLException will be thrown if the
preparedStatement has parameters and a parameter was not.
--------------------------------------------------
Message Id: 1114001
Message Type: Change Request
Version: 73.00.21
ResultSet.getType() works now proper.
ResultSet.setFetchSize(negative)throws a SQLException.
Calling ResultSet.Last(); ResultSet.isLast(); on an empty ResultSet return
false.
--------------------------------------------------
Message Id: 1114002
Message Type: Change Request
Version: 73.00.21
PreparedStatement.executeBatch() with a select statement throws a
SQLException.
Statement.executeBatch() with a select statement throws a SQLException.
CallableStatement.executeBatch() with a procedure with an OUT parameter
throws a SQLException.
CallableStatement.executeBatch() with a procedure with an INOUT parameter
throws a SQLException.
executeBatch() now returns the correct UpdateCount values.
--------------------------------------------------
Message Id: 1114608
Message Type: Change Request
Version: 73.00.23
Priority: 1
Responsible: Marco Paskamp
In oracle mode a PreparedStatement.setString("") should always insert/update
the NULLvalue instead of an empty string.
--------------------------------------------------
Message Id: 1114960
Message Type: Error
Version: 73.00.23
Priority: 1
Responsible: Marco Paskamp
Fixes the bug in PreparedStatement.executeBatch that a ClassCastException
will be thrown or the initial value will be inserted in the database if a
parameters was not set. Now a BatchUpdateException will be thrown if a
parameter is missing.
--------------------------------------------------
Message Id: 1110549
Message Type: Error
Version: 73.00.23
Priority: 2
Responsible: Marco Paskamp
The column TYPE_NAME in DatabaseMetadata.getColumns() and
DatabaseMetadata.getTypeInfo() returns the same value for same types. The
returnvalues for TYPE_NAME are now valid column description in "CREATE
TABLE"-commands.
--------------------------------------------------
Message Id: 1114606
Message Type: Change Request
Version: 73.00.23
Priority: 2
Responsible: Marco Paskamp
ResultSetMetaData.getColumnDisplaySize() returns the correct maximum column
length for long columns (2147483647 or 1073741824 for a unicode database).
Best regards,
Marco
----------------------------------------------
Marco PASKAMP
SAP DB, SAP Labs Berlin
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
