You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you use Statement.executeBatch with first a succesful UPDATE statement and the second statement is a DDL then the returned update count of the DDL is the same as the UPDATE statement.
Example, the following statements are the input for executeBatch:
UPDATE TOPIC SET TPC_NAME = "Test";
ALTER TABLE LOGDBSCRIPT ADD LDBS_TEST6 INTEGER;
The UPDATE statement results in 6 updates, so the update count of that statement equals to 6.
The DDL statement will have no update count so the expected update count should be -2 (according to the specs).
However, the update count of this statement is 6. It seems that in case of a DDL the update count of the last successful UPDATE statement is used.
Submitted by: rockxwre (rockxwre)
Assigned to: Roman Rokytskyy (rrokytskyy)
If you use Statement.executeBatch with first a succesful UPDATE statement and the second statement is a DDL then the returned update count of the DDL is the same as the UPDATE statement.
Example, the following statements are the input for executeBatch:
UPDATE TOPIC SET TPC_NAME = "Test";
ALTER TABLE LOGDBSCRIPT ADD LDBS_TEST6 INTEGER;
The UPDATE statement results in 6 updates, so the update count of that statement equals to 6.
The DDL statement will have no update count so the expected update count should be -2 (according to the specs).
However, the update count of this statement is 6. It seems that in case of a DDL the update count of the last successful UPDATE statement is used.
Commits: cdc01d9
The text was updated successfully, but these errors were encountered: