[ http://issues.apache.org/jira/browse/DERBY-1501?page=all ]
Knut Anders Hatlen resolved DERBY-1501.
---------------------------------------
Fix Version/s: 10.3.0.0
Resolution: Fixed
With the check-in of DERBY-1610, embedded and client behave consistently.
> PreparedStatement#setNull(int parameterIndex, int sqlType) throws SQL
> Exception if given sqlType is LONGVARBINARY in embedded mode
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1501
> URL: http://issues.apache.org/jira/browse/DERBY-1501
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.1.1.0
> Environment: WindowsXP
> Reporter: Markus Fuchs
> Fix For: 10.3.0.0
>
> Attachments: ByteArrayTest.java
>
>
> 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.
--
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
