This repository has been archived by the owner on Jan 28, 2021. It is now read-only.
StatusMessage should be associated with transactionUid + sequence, not just transactionUid #88
Comments
|
Also, add a secondary index (non-unique) on (transactionId, sequence) |
danhaywood
added a commit
that referenced
this issue
Jul 9, 2018
danhaywood
added a commit
that referenced
this issue
Jul 9, 2018
- StatusMessage and PublishedEvent now implement new RepresentsInteractoinMemberExecutoin interface - improve mixins to check for this subinterface, if so then use to query also by sequence - in particular, this means that can find the PublishedEvent for a StatusMessage
danhaywood
added a commit
that referenced
this issue
Jul 10, 2018
of PublishedEvent and StatusMessage, otherwise get hsqldb errors under DN 4.1... fails to construct DDL to create table correctly when running integ tests
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: