[DERBY-1501] PreparedStatement#setNull(int parameterIndex, int sqlType) throws SQL Exception if given sqlType is LONGVARBINARY in embedded mode

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.1.1.0
• Fix Version/s: 10.3.1.4
• Component/s: JDBC
• Environment: WindowsXP
• Assignee: Unassigned
• Reporter: Markus Fuchs
• Created: 12/Jul/06 02:49
• Updated: 21/Jan/11 17:49
• Resolved: 08/Oct/06 18:26

Description

When inserting a row into following table

BYTEARRAY_TEST( ID int, BYTEARRAY_VAL blob)

PreparedStatement#setNull(int parameterIndex, int sqlType) throws SQL Exception if given sqlType is LONGVARBINARY. You must give sqlType BLOB to make the insert work. The same test works using sqlType LONGVARBINARY in network mode. The following combinations don't work:

Column type sqlType not working mandatory sqlType
BLOB LONGVARBINARY BLOB
CLOB LONGVARCHAR CLOB

The issue here is that first Derby behaves differently in network and embedded mode. And secondly, should accept LONGVARBINARY/LONGVARCHAR for BLOB/CLOB columns.

Issue Links

• incorporates: DERBY-1494 PreparedStatement.setNull(int, int) checks type compatibility on embedded, but not on the client
• is part of: DERBY-1610 Resolve difference of type compatibility between Embedded and NetworkServer/NetworkDriver
• is related to: DERBY-310 Document and/or change Derby client code to match behavior with Embedded driver where possible.