Repository navigation
fix(model): track in-place mutations of collection columns - #606
Merged
Merged
Conversation
Draft
FCO
force-pushed
the
split/collection-dirty-tracking
branch
from
October 27, 2026 23:46
8d0ab30 to
a1d928f
Compare
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.
Detect in-place changes to Positional, Associative and Json columns when
.^saveis called. Deep snapshots retain original mutable values and are refreshed after clean-up or partial refresh.Backport the change onto the current storage interfaces so it does not require the separate hydration/performance changes. Cover nested edits, typed collections, reassignment, independent instances and refresh behavior.
Validation:
RAKUDO_RAKUAST=0 prove6 -lj4 tpassed (Files=99, Tests=1261).Split out of #603. This branch is based directly on
masterand can be reviewed and merged without another split PR.