Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
P2 (Critical with Workaround)
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.6.0.0
-
Component/s: None
-
Labels:None
-
Target Version/s:
-
Doc Impact:Complete
-
Doc Impact Details:Document the fact that data is committed after every batch, unless autocommit is enabled. New config param in Advanced tab: 'Batch Commit'
-
Testing Status:STF Testing Required
-
Testing Description:Check that you can see data in the database when autocommit is disabled.
Description
JDBC Executor allows the user to specify a 'query', which can be any SQL, such as INSERT INTO my_table blah blah. The problem is that the executor never calls commit, so you don't see the data.
Workaround is to configure autocommit, but this commits after every SQL statement. We should call commit after every batch.