[DERBY-2430] setObject(int targetType, Blob source) and setObject(int targetType, Clob source) should disallow updates on all targetTypes except BLOB and CLOB respectively

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 10.3.1.4
• Component/s: Network Client
• Environment: All
• Issue & fix info: Release Note Needed
• Assignee: V.Narayanan
• Reporter: V.Narayanan
• Created: 09/Mar/07 07:50
• Updated: 16/Jun/07 16:26
• Resolved: 16/Jun/07 16:26

Description

updateBlob(int columnIndex, Blob x), updateClob(int columnIndex, Clob x) can be implemented by forwarding calls to setObject(int targetType, Blob source), setObject(int targetType, Clob source). If this this done then

1) updateClob on a CHAR/VARCHAR/LONG VARCHAR column throws an exception on the Embedded Driver but not on the NetworkClient
2) updateBlob works on a CHAR/VARCHAR/LONG VARCHAR FOR BIT DATA throws an exception on the Embedded Driver but not on the NetworkClient

From what the JDBC 4.0 spec says (pg 198 table b-5) the Embedded behaviour seems to be correct.

This can be fixed by Matching Embedded behaviour. This would involve throwing an exception in the cases mentioned above

Issue Links

• blocks: DERBY-2443 Implement ResultSet updateClob/updateBlob methods on the NetworkClient
• is related to: DERBY-1610 Resolve difference of type compatibility between Embedded and NetworkServer/NetworkDriver