Details
-
Type:
Bug
-
Status: Done (View workflow)
-
Priority:
Highest
-
Resolution: Done
-
Affects Version/s: R3 Corda 3.0 Dev Preview 3, Corda 3.1
-
Fix Version/s: R3 Corda 3.0 Dev Preview 3, Corda 3.3
-
Component/s: None
-
Labels:None
-
Severity:Medium
-
Target Version/s:
-
Feature Team:Notaries and Performance
-
Sprint:Notaries and Performance
Description
A recent change to transaction recording reverted a change to only update the vault with newly inserted transactions only. Currently we get primary key violations in the database for vault tables when a duplicate transaction is inserted.
We should also add a unit test to make sure we don't revert this filter.
Duplicate transactions are a valid scenario due to parallel transaction resolution.
Attachments
Issue links
- mentioned in
-
Page Loading...