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.
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
Allow frozen Realms to be opened with additive schema changes #6693
Allow frozen Realms to be opened with additive schema changes #6693
Changes from 3 commits
fe11943
cb26716
515c1a1
d5a8995
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see you're comparing the local schema with the frozen realm's schema. Should we also check the column indexes (e.g.
get_column_name()
) or should comparing the schemas be sufficient? Does comparing schemas also verify the order of the properties?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The schema has a strongly ordered equality check built in to operator==. I verified that this test failed without the fix. However, it may not be appropriate to rely on that internal behaviour, so I added some extra checks here to ensure that the intent of the test survives any future changes to
Schema::operator==()
.