[ 
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12429256 ] 
            
Knut Anders Hatlen commented on DERBY-1610:
-------------------------------------------

Hi Tomohito,

The BatchUpdateException indicates that the error happens when executeBatch() 
is invoked, not when setXXX() or addBatch() is called. I think this is OK, but 
it would of course be better if the exception were raised in setXXX().

If you want to ignore these errors in parameterMapping.java, you could wrap 
each call to executeBatch() like this:

try {
    psi.executeBatch();
} catch (BatchUpdateException bue) {
    SQLException reason = bue.getNextException();
    throw (reason == null) ? bue : reason;
}

Also, do you think a release note is needed for this issue? If I understand 
correctly, the client driver (and possibly JCC) will throw an exception in 
situations where they didn't throw an exception before.

> 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

        

Reply via email to