Replies: 1 comment
-
|
You're right about missing unlink in the API. Direct manipulation or adding project-specific functionality to the event store client adapter are the best options now. Regarding possible drawbacks — I've summarized my concerns here. I think it is safer to rewrite the stream, omitting particular events. This way you'll always get continuous positions. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We have been using the event store to keep track of events regarding a tree like structure. This has been working great, but we have started noticing some very weird performance issues.
In our code we noticed that we were doing something like this (pseudo-code)
Our projection logic handles these case properly (lots of IFs), but you can imagine that we select WAY more events to project a folder than needed.
It is not clear anymore why this was done (maybe we thought this would be useful down the line? or we didn't understand event sourcing exactly)... doesn't matter.
We now want to unlink these events (pseudo code)
At this time we can not find a way to unlink these events in the docs. Should we just do a direct delete in the database? Any caveats we need to worry about?
Beta Was this translation helpful? Give feedback.
All reactions