| Field |
Original Value |
New Value |
|
Description
|
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.
|
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.
|
|
Summary
|
Documentation of different batchExecute behavior between embedded and DerbyNetClient needed
|
Documentation of different executeBatch error handling between embedded and DerbyNetClient needed
|
Improvement
Closed
Minor
Documentation of different executeBatch error handling between embedded and DerbyNetClient needed
