You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If it's available, it can be worth it to store commit ID (or "transaction id") in event's metadata, in order to know which events were published in one transaction, as a whole.
It probably would need some RubyEventStore support, but the core of that feature would be for the Repository to actually provide transaction ID. That can be used alongside for example with building read models or other DB transactions, to see which changes were grouped together.
(note from one of KanDDDinsky talks, I don't remember which one -- I think Dennis Doomen's one, about projections)
This discussion was converted from issue #1443 on May 15, 2025 16:31.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
If it's available, it can be worth it to store commit ID (or "transaction id") in event's metadata, in order to know which events were published in one transaction, as a whole.
It probably would need some RubyEventStore support, but the core of that feature would be for the Repository to actually provide transaction ID. That can be used alongside for example with building read models or other DB transactions, to see which changes were grouped together.
(note from one of KanDDDinsky talks, I don't remember which one -- I think Dennis Doomen's one, about projections)
Beta Was this translation helpful? Give feedback.
All reactions