You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2007/05/27 23:37:16 UTC
[jira] Updated: (DERBY-1501) PreparedStatement#setNull(int
parameterIndex, int sqlType) throws SQL Exception if given sqlType is
LONGVARBINARY in embedded mode
[ https://issues.apache.org/jira/browse/DERBY-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-1501:
--------------------------------------
Derby Info: (was: [Existing Application Impact])
Switching off existing application impact. The actual change went in with DERBY-1610, and that one should have the application impact, and release note.
> PreparedStatement#setNull(int parameterIndex, int sqlType) throws SQL Exception if given sqlType is LONGVARBINARY in embedded mode
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1501
> URL: https://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.
-
You can reply to this email to add a comment to the issue online.