New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

danhaywood opened this Issue Jul 5, 2018 · 1 comment


1 participant

danhaywood commented Jul 5, 2018

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 danhaywood added this to In Progress in incode-platform (project) Jul 5, 2018


This comment has been minimized.

Show comment
Hide comment

danhaywood Jul 9, 2018


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


danhaywood commented Jul 9, 2018

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

@danhaywood danhaywood moved this from In Progress to Resolved / Closed in incode-platform (project) Jul 9, 2018

danhaywood added a commit that referenced this issue Jul 9, 2018

#88 - fixes up mixins for HasTransactionId
- 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

#87 and #88 - need to fix position for all properties
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 join this conversation on GitHub. Already have an account? Sign in to comment