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/02/07 18:30:06 UTC
[jira] Updated: (DERBY-2301) Documentation of different
executeBatch error handling between embedded and DerbyNetClient needed
[ https://issues.apache.org/jira/browse/DERBY-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-2301:
--------------------------------------
Description:
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.
was:
There is a difference in batchExecute() behavior on error between embedded and DerbyNetClient.
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.
Summary: Documentation of different executeBatch error handling between embedded and DerbyNetClient needed (was: Documentation of different batchExecute behavior between embedded and DerbyNetClient needed)
> 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.