You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org> on 2006/10/08 20:01:20 UTC
[jira] Resolved: (DERBY-1494) PreparedStatement.setNull(int, int)
checks type compatibility on embedded, but not on the client
[ http://issues.apache.org/jira/browse/DERBY-1494?page=all ]
Knut Anders Hatlen resolved DERBY-1494.
---------------------------------------
Fix Version/s: 10.3.0.0
Resolution: Fixed
After the check-in of DERBY-1610, both embedded and client check type compatibility.
> PreparedStatement.setNull(int, int) checks type compatibility on embedded, but not on the client
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-1494
> URL: http://issues.apache.org/jira/browse/DERBY-1494
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.2.1.6
> Reporter: Knut Anders Hatlen
> Priority: Minor
> Fix For: 10.3.0.0
>
>
> When PreparedStatement.setNull(int, int) is called, the embedded driver will check whether the sqlType parameter specifies a type which is compatible with the actual parameter type. If the types are not compatible, an exception is thrown. The client driver does not check whether the types are compatible, and does not throw an exception.
> Both drivers behave according to the spec, but one of them should be changed to match the other one.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira