Adam Saghy created FINERACT-1946:
------------------------------------
Summary: Random order of primary key generation at
reverse-replaying multiple transactions
Key: FINERACT-1946
URL: https://issues.apache.org/jira/browse/FINERACT-1946
Project: Apache Fineract
Issue Type: Bug
Affects Versions: 1.8.3
Reporter: Adam Saghy
Due to the nature of JPA specification the order of the persistence of the
managed entities are not defined.
When multiple entities are reverse-replayed the new entities will be persisted
not in a defined order.
Since the loan transactions are ordered primarily based on transaction id and
secondarily based on the primary key if multiple transactions with the same
transaction date got reverse-replayed the order of the transactions can be
switched and not consistent.
This could be a major problem, however it can be considered as an edge case in
most situations.
*Acceptance criteria*
* The order of the transactions shall be consistent after the reverse-replaying
* The order of the reverse-repalyed transactions shall match with the original
order
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
