Release Notes for IBM Informix JDBC Driver 2.21.JC3

06/15/2002

Table of Contents

  1. Overview of Release Notes
  2. IBM Informix Dynamic Server Compatibility
  3. Configuration
  4. New Features
  5. JDBC Behavior with JDK 1.4
  6. Database Connections in the Demo Programs
  7. Fixed Problems
  8. Known Problems
  9. Limitations
  10. XML Parser
  11. Acknowledgements
  12. Patch Information (certified platforms)

I. Overview of Release Notes

The purpose of these release notes is to make you aware of any special actions required to configure and use the IBM Informix JDBC Driver on your computer. This file also describes new features and feature differences from earlier versions of this product and other IBM Informix products and how these differences affect current products. In addition, this file contains information about known bugs and their workarounds. This release notes document is not intended to be all-inclusive; it should be used as an addendum to the IBM Informix JDBC Driver Programmer's Guide, Version 2.21, which provides thorough information about product features and behavior. These release notes are written for Java programmers who use the JDBC API to connect to IBM Informix databases via the IBM Informix JDBC Driver.

II. IBM Informix Dynamic Server Compatibility

IBM Informix JDBC Driver 2.21 is compatible with the following server versions:

III. Configuration

To use the IBM Informix JDBC Driver directly, you must have a JDK 1.2 (or later) package on your platform. Please refer to http://java.sun.com/products/jdbc/ for details.

IV. New Features

IBM Informix JDBC Driver Version 2.21 includes new features, each of which is fully documented in the IBM Informix JDBC Driver Programmer's Guide.

V. JDBC Behavior with JDK 1.4

Due to a Sun Microsystem Java (TM) Bug 4361575 fix in JDK 1.4, UDT/UDR manager helper classes included in the ifxtools.jar in the JDBC driver are not accessible from a packaged class. In previous releases, JDBC driver UDT/UDR manager helper classes from ifxtools.jar were not part of any package/named namespace, thus users with JDK 1.4 will not be able to use these classes from any packaged class or named namespace.
 

As a part of a fix, the following change was done in the 2.21.JC3 release of JDBC driver:
All the helper classes for UDT/UDR in ifxtools.jar are now part of the namespace / package called udtudrmgr. The unpackaged version of these classes is also included for backward compatibility with JDK 1.3 and JDK1.2. Users trying to use UDT/UDR manager classes in JDK 1.4 from the packaged class will need to use following kind of import statements in their programs:

VI. Database Connections in the Demo Programs

Except for the pickaseat demo, the examples listed in the IBM Informix JDBC Driver Programmer's Guide, Version 2.21, use the DriverManager.getConnection() method to get a database connection. Sun Microsystems recommends using a DataSource object instead. For more information, refer to the Sun documentation and to the README.TXT file in the demo/pickaseat directory.

VII. Fixed Problems

Bug # 152800

SETFETCHSIZE METHOD DOES NOT SET NUMBER OF ROWS THAT HAS BEEN SPECIFIED                            

 

Bug # 152843

GETPROCEDURECOLUMNS METHOD THROWS JAVA.SQL.SQLEXCEPTION WHEN USER NAME IS GIVEN AS PARAMETER       

 

Bug # 153170

BATCHUPDATE DOES NOT WORK WITH BYTE TEXT COLUMNS EVEN WITH THE NEW BATCHUPDATE PROTOCOL - HANGS IF UNDERLYING COLUMN IS BLOB/CLOB                    

 

Bug # 153871

USING XADATASOURCE FOR ANSI DATABASES WHEN CONNECTED AS USER "INFORMIX" GIVES ALREADY IN TRANSACTION ERROR                                            

 

Bug # 153982

JDBC SETBIGDECIMAL METHOD MISBEHAVES WHEN CALLED FOR AN ARGUMENT DESTINED FOR A SUBQUERY EMBEDDED IN A SET-CLAUSE OF AN UPDATE STATEMENT            

 

Bug # 154062

JDBC 2.20.JC2 UPDATEROW THROWS NULLPOINTEREXCEPTION WHEN BACKEND IS AN SE AND SETNULL IS CALLED PREVIOUSLY                                          

 

Bug # 154493

SELECTING ROW TYPES WILL RETURN INCORRECT RESULTS FOR AN INTEGER FIELD FOLLOWING A LVARCHAR (UDT) FIELD WITHIN THAT ROW IF LVARCHAR IS NULL       

 

Bug # 154494

ARRAYINDEXOUTOFBOUNDSEXCEPTION OR OUTOFMEMORYERROR WHEN ATTEMPTING TO READSTRING FROM THE LLD_LOCATOR SQLDATA                                        

 

Bug # 154499

AN EXCEPTION IS THROWN AND ERROR 79865 IS RAISED WHEN QUERYTIMEOUT IS SET ALTHOUGH THE QUERY HAS COMPLETED AND THE STATEMENT IS CLOSED               

 

Bug # 154550

JDBC DOES NOT INSERT/RETRIEVE DATA CORRECTLY FOR KOREAN LOCALE.                                    

 

Bug # 154598

IF THE STATEMENT IS CREATED BEFORE STARTING XA TRANSACTION AND EXECUTED AFTER THAT, ACCESS TO RESULT SET FAILS WITH "CURSOR NOT OPEN" ERROR.          

 

Bug # 154599

XACONNECTION.CLOSE() DOES NOT CLOSE THE CONNECTION TO THE SERVER. IT CLOSES ONLY THE DATABASE.     

 

Bug # 154608

GETINDEXINFO METHOD IN IFXDATABASEMETHOD DOES NOT RETURN INFO IF INDEX IS BUILD IN DESCENDING ORDER

 

Bug # 154631

BULK INSERT WITH JBDC RESULTS IN DATA CORRUPTION 

 

Bug # 154656

PREPARING A SQL STATEMENT THAT HAS A QUESTION MARK IN THE LITERAL STRING THAT IS PASSED AS AN ARGUMENT THROWS AN EXCEPTION.                          

 

Bug # 154801

PERFORMING EXECUTEBATCH() ON SAME PREPAREDSTATEMENT MULTIPLE TIMES CAUSES SAME BLOCK OF DATA TO BE INSERTED IF IFX_SET_BATCH_UPDATE = 0               

 

Bug # 155061

PERFORMANCE IS SLOW IN ADDBATCH METHOD OF STATEMENT OBJECT.                                        

 

Bug # 155100

JDBC GETCOLUMNS METHOD FAILS TO REPORT THE COLUMNS OF A SYNONYM TYPE TABLE.                       

 

Bug # 155102

GETTABLES METHOD FAILS TO DISTIGUISH DIFFERENT TABLE TYPES, IT REPORTS ALL TABLES AS TABLES OF TYPE SYNONYM, IT BEHAVES THE SAME FOR OTHER TABLE TYPES

 

Bug # 155149

2.2X JDBC RETURNS INCORRECT LENGTH OF SCHEMA NAME IN METADATA                                       

 

Bug # 155542

INCORRECT DATE IS INSERTED INTO DATE COLUMN WHEN BULK INSERT IS USED (REPORTED BY AGS)             

 

Bug # 155670

MEMORY LEAK WHEN USING JNDI, CONNECTION POOLING  

 

Bug # 155770

IF YOU SET IFX_AUTOFREE IN THE URL YOU ARE UNABLE TO USE THE IFXSTATEMENT.SETAUTOFREE() TO DISABLE IT FOR INDIVIDUAL STATEMENTS.                     

 

Bug # 156244

CANNOT USE UDT/UDR MANAGER CLASSES FROM IFXTOOLS.JAR IN JDK 1.4 

                                 

Bug # 156272

NULL POINTER EXCEPTION CALLING STATEMENT.CANCEL() WHEN CONNECTION IS MADE THROUGH A PROXY SERVER   

 

Bug # 156367

CALLING PREPAREDSTATEMENT.SETOBJECT() INSERTS NULL VALUE IN DATABASE FOR FLOAT OBJECT TYPE         

 

Bug # 156411

CALLING DATABASEMETADATA.GETCOLUMNS() IN MULTITHREADED ENVIRONMENT THROWS CANNOT CREATE OBJECT OF JDK1.2 CLASS COLLECTIONS EXCEPTION                  

VIII. Known Problems

This section describes the known problems with this release of IBM Informix JDBC Driver and shows how to work around these problems. 

IX. Limitations

Please refer to the IBM Informix JDBC Driver Programmer's Guide, Version 2.21 for complete list of unsupported methods.

X. XML Parser

IBM Informix JDBC Driver bundles xerces.jar along with the other driver jar files. This xerces.jar is part of the IBM XML4J version 3.2.1 parser and is developed by Apache Software Foundation (http://www.apache.org).

XI. Acknowledgements

This product includes software developed by the Apache Software Foundation (http://www.apache.org/). The Apache software includes xerces.jar. The Apache copyright notice follows in its entirety.

The Apache Software License, Version 1.1 Copyright (c) 1999 The Apache Software Foundation. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.
  4. The names "Xerces" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org.
  5. Products derived from this software may not be called "Apache," nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.

THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.


This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright (c) 1999, International Business Machines, Inc., http://www.ibm.com. For more information on the Apache Software Foundation, please see http://www.apache.org.. 


Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.