[CAUSEWAY-2555] [WON'T FIX] EntityChanges (as consumed by EntityChangesSubscriber) should associate with transaction, not interaction?

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Fix Version/s: 2.0.0-M6
• Component/s: Core
• Assignee: Unassigned
• Reporter: Daniel Keir Haywood
• Created: 01/Mar/21 09:23
• Updated: 25/Aug/21 14:33
• Resolved: 26/Jul/21 12:33

Description

The docs say that EntityChanges releates to a transaction, but it only has a uniqueId which identifies the parent interaction (there can be many transactions per interaction).  So, we're missing a sequence.

EntityChanges also has a reference to ChangesDto, which contains a sequence, so I think the information is there.

There is also a TransactionId which is the tuple of uniqueId (for interaction) and sequence, so in fact EntityChanges should probably have a field of type TranscationId rather than UUID uniqueId.

 

~~~

Similarly, EntityPropertyChange has both a uniqueId and a sequence, so they should be replaced by a field of type TransactionId instead.