db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2301) Documentation of different executeBatch error handling between embedded and DerbyNetClient needed
Date Wed, 07 Feb 2007 17:30:06 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471035
] 

Myrna van Lunteren commented on DERBY-2301:
-------------------------------------------

Indeed. I changed the batchExecute to executeBatch in description and summary.

> Documentation of different executeBatch error handling between embedded and DerbyNetClient
needed
> -------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2301
>                 URL: https://issues.apache.org/jira/browse/DERBY-2301
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.3.0.0
>            Reporter: Myrna van Lunteren
>            Priority: Minor
>
> There is a difference between embedded and networkserver/DerbyNetClient in how error
situations when using java.sql.Statement.executeBatch() and related batch methods are handled.
> Embedded 'stops' processing on error, the Client continues. The second mechanism was
added as ok behavior with JDBC3.0, I believe, and both are acceptable approaches.
> However, it could be disconcerting to an unsuspecting user, seeing as both drivers come
from the 'same' codeline, and it should be listed under the differences in the Server and
Admin Guide.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message