|
Quick Lists
|
|
Bug ID:
|
4522957
|
|
Votes
|
0
|
|
Synopsis
|
Incorrect new method "setNull" in java.sql.CallableStatement (beta3)
|
|
Category
|
jdbc:implementation
|
|
Reported Against
|
merlin-beta3
|
|
Release Fixed
|
1.4(merlin-rc1)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
3-Medium
|
|
Related Bugs
|
4527796
|
|
Submit Date
|
05-NOV-2001
|
|
Description
|
c:\>java -version
java version "1.4.0-beta3"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta3-b84)
Java HotSpot(TM) Client VM (build 1.4.0-beta3-b84, mixed mode)
Bug is found in JDK 1.4 beta3 ( there is no drop-down choice for beta3)
In JDK 1.4 beta3, the java.sql package now contains the JDBC 3.0 functionality.
CallableStatement.java contains the new JDK 1.4 method:
void setNull(int paramIndex, int sqlType, String typeName)
throws SQLException;
However, this method is already defined in PreparedStatement.java!
From the surrounding context, I think the new JDK 1.4 method signature in
CallableStatement.java should be:
void setNull(String parameterName, int sqlType, String typeName)
throws SQLException;
(Review ID: 135025)
======================================================================
|
|
Work Around
|
N/A
|
|
Evaluation
|
This signature of setNull(int, int, String) in CallableStatement is invalid and uncorrectly over-rides the setNull method provided in PreparedStatement.
API needs to be modified to correct this error as follows:
setNull(String, int, String);
xxxxx@xxxxx 2001-11-12
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
