[DERBY-1494] PreparedStatement.setNull(int, int) checks type compatibility on embedded, but not on the client

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.2.1.6
• Fix Version/s: 10.3.1.4
• Component/s: JDBC
• Assignee: Unassigned
• Reporter: Knut Anders Hatlen
• Created: 10/Jul/06 15:17
• Updated: 10/Oct/06 09:59
• Resolved: 08/Oct/06 18:01

Description

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.

Issue Links

• is part of: DERBY-1501 PreparedStatement#setNull(int parameterIndex, int sqlType) throws SQL Exception if given sqlType is LONGVARBINARY in embedded mode
• is part of: DERBY-1610 Resolve difference of type compatibility between Embedded and NetworkServer/NetworkDriver
• is part of: DERBY-310 Document and/or change Derby client code to match behavior with Embedded driver where possible.