|
Quick Lists
|
|
Bug ID:
|
6462628
|
|
Votes
|
0
|
|
Synopsis
|
Changes needed to Types.java for new datatypes to avoid collisions with Oracle data types
|
|
Category
|
jdbc:implementation
|
|
Reported Against
|
|
|
Release Fixed
|
mustang(b98)
|
|
State
|
10-Fix Delivered,
Needs Verification,
bug
|
|
Priority:
|
2-High
|
|
Related Bugs
|
6467799
|
|
Submit Date
|
22-AUG-2006
|
|
Description
|
JDBC defines a bunch of int constants in java.sql.Types. These ints
are used as arguments to assorted methods like getObject and
registerOutParameter. Oracle defines some additional int constants in
customer .jdbc.OracleTypes that identify Oracle specific types. The JDBC
4.0 spec defines six new types. Unfortunately the int values chosen
for four of those new types conflict with values defined in
OracleTypes. Since ints are ints, there is no way to distinguish
between them. The driver cannot tell the difference between
s.registerOutParameter(n, Types.NCHAR);
and
s.registerOutParameter(n, OracleTypes.ROWID);
The two have the same int value.
The following redefinitions of the
java.sql.Types constants that avoid any incompatibility with OracleTypes.
public final static int NCHAR = -15; // was -8
public final static int NCLOB = 2011; // was 2007
public final static int NVARCHAR = -9; // ok
public final static int LONGNVARCHAR = -16; // was -10
public final static int ROWID = -8; // was 2008
public final static int SQLXML = 2009; // ok
Posted Date : 2006-08-22 17:31:19.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
Must be done for GA
Posted Date : 2006-08-22 17:35:04.0
changes have been made to Types.java
Posted Date : 2006-08-23 18:57:43.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |