search

incodehq / incode-platform

Combines incode.org modules and isisaddons.org into a single set of modules.
http://platform.incode.org
Apache License 2.0
8 stars 9 forks source link

StatusMessage should be associated with transactionUid + sequence, not just transactionUid #88

Open danhaywood opened 6 years ago

danhaywood commented 6 years ago

There can be many interactions within a single transaction. Most notably this occurs when the WrapperFactory is used to invoke an action on a collection of objects; each of these is a separate interaction execution within the overall transaction, and will emit its own interaction execution through the PublisherService.

If we want to associate StatusMessage's with a particular interaction execution (when there are many), then the StatusMessage API (and corresponding entity) need to be extended in order to use both parts of the primary key of PublishedEvent.

danhaywood commented 6 years ago

Also, add a secondary index (non-unique) on (transactionId, sequence)