Fix optimize dropping only-last-event sub queries - #919
Merged
Merged
Conversation
SubQuery::includes() treated an onlyLastEvent sub query with broader filters as covering a narrower onlyLastEvent one. The last event tagged `a` is not necessarily the last event tagged `a` and `b`, so Query::optimize() removed the narrower sub query and the projection behind it never got its event. An onlyLastEvent sub query now only includes another one if both match exactly the same events.
|
Hello 👋 here is the most recent benchmark result:
This comment gets update everytime a new commit comes in! |
DanielBadura
approved these changes
Oct 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Query::optimize()removed anonlyLastEventsub query when anotheronlyLastEventsub query had broader filters, e.g.['a']vs.['a', 'b']. But the last event taggedais not necessarily the last event taggedaandb. SinceCompositeProjection::query()always optimizes, a decision model with twolastEventIsEnough()projections like that silently built the narrower one from its initial state.SubQuery::includes()now only lets anonlyLastEventsub query include another one if both match exactly the same events. A regular sub query can still absorb a narroweronlyLastEventone, since it loads all events anyway.