Replaying in 2 steps using a `force-replay` switch loses data from `account_operations` table
In both cases replaying up to 5mln blocks is done in 2 steps. In a second case a number of records in account_operations table is smaller.
Case 1:
./hived -d DIR --replay-blockchain --stop-replay-at-block 4100000 --exit-before-sync
./hived -d DIR --replay-blockchain --stop-replay-at-block 5000000 --exit-before-syncresults( type of data, number of records ):
- blocks:
5000000 - accounts:
92462 - transactions:
6961192 - transactions_multisig:
450 - operations:
19792321 - account_operations:
29489856
Case 2:
./hived -d DIR --force-replay --stop-replay-at-block 4100000 --exit-before-sync
./hived -d DIR --force-replay --stop-replay-at-block 5000000 --exit-before-syncresults( type of data, number of records ):
- blocks:
5000000 - accounts:
92462 - transactions:
6961192 - transactions_multisig:
450 - operations:
19792321 - account_operations:
20208620