[ http://issues.apache.org/jira/browse/DERBY-1610?page=all ]
Tomohito Nakayama updated DERBY-1610:
-------------------------------------
Attachment: DERBY-1610_2.diff
parameterMapping.diff
I upload DERBY-160_2.diff.
With this patch, errors happens in intended cases at
jdbcapi/parameterMapping.java.
That difference of errors in parameterMapping.out is uploaded as
parameterMapping.diff too.
However, there remains concerning points in the error.
In the case of batch processing, there found next exception like as next.
> setNull with batching support(BLOB) SQLSTATE(XJ208):
> org.apache.derby.client.am.BatchUpdateException: Non-atomic batch failure.
> The batch was submitted, but at least one exception occurred on an individual
> member of the batch. Use getNextException() to retrieve the exceptions for
> specific batched elements.
> SQLSTATE(22005): java.sql.SQLException: Error for batch element #0: An
> attempt was made to get a data value of type 'CLOB' from a data value of type
> 'BLOB'.
I think these errors should be ignored in jdbcapi/parameterMapping.java ,but
not sure yet.
I will continue surveying about them.
> Updating column typed as CHAR to value passed via setBinaryStream(notNull) is
> failed because of imcompatiblity of types though it was not taken as error
> when setBinaryStream(null)
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1610
> URL: http://issues.apache.org/jira/browse/DERBY-1610
> Project: Derby
> Issue Type: Bug
> Components: Network Server, Network Client
> Reporter: Tomohito Nakayama
> Assigned To: Tomohito Nakayama
> Attachments: DERBY-1610.diff, DERBY-1610_2.diff,
> parameterMapping.diff, parameterMapping.diff, TestNullChar.java
>
>
> There exists difference between updating character typed column to value
> passed via setBinaryStream(notNullValue) and updating the column to value
> passed via setBinaryStream(null).
> This difference is problematic because it does not exist in Embedded mode.
--
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
