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
{{ message }}
This repository has been archived by the owner on Aug 23, 2021. It is now read-only.
Shouldn't all the
executeBatch()
be called out of these if-blocks?oltpbench/src/com/oltpbenchmark/benchmarks/tpcc/TPCCLoader.java
Lines 200 to 205 in dc32a26
oltpbench/src/com/oltpbenchmark/benchmarks/tpcc/TPCCLoader.java
Lines 334 to 338 in dc32a26
oltpbench/src/com/oltpbenchmark/benchmarks/tpcc/TPCCLoader.java
Lines 509 to 515 in dc32a26
oltpbench/src/com/oltpbenchmark/benchmarks/tpcc/TPCCLoader.java
Lines 655 to 667 in dc32a26
Because when this
commit()
is called in the end, the prepared statements in the last turns, are never taken account.oltpbench/src/com/oltpbenchmark/api/Loader.java
Line 64 in dc32a26
.. and
D_NEXT_O_ID
is getting hardcoded here.oltpbench/src/com/oltpbenchmark/benchmarks/tpcc/TPCCLoader.java
Line 374 in dc32a26
.. which, in turn, violates TPCC consistency conditions 2 and 3 after loading phase and execution phase respectively.
The text was updated successfully, but these errors were encountered: