[ http://issues.apache.org/jira/browse/DERBY-1494?page=comments#action_12421305 ] Knut Anders Hatlen commented on DERBY-1494: -------------------------------------------
DERBY-1501 has many comments that are relevant to this issue. They indicate that the behaviour of the embedded driver is the expected behaviour, and that the wording will be changed in JDBC 4.0. > 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.0.0 > Reporter: Knut Anders Hatlen > Priority: Minor > > 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
