-
Notifications
You must be signed in to change notification settings - Fork 165
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
Ensure column keys in virgin tables are unique on 32bit devices #4051
Conversation
Does this fix already upgraded files? |
No :-(. The files that has been upgraded and end up being inconsistent cannot be rescued. |
Or probably more correct: The files can be fixed - but not automatically. It would impose a very big runtime overhead to run a complete consistency check on every realm open. |
Could we make an option to run a consistency check? Would that be a bad idea? I'm not too fond of bloating the API with those "debugging" features... How many have experienced this though? |
@@ -5,7 +5,7 @@ | |||
|
|||
### Fixed | |||
* <How to hit and notice issue? what was the impact?> ([#????](https://github.com/realm/realm-core/issues/????), since v?.?.?) | |||
* None. | |||
* Files upgraded on 32-bit devices could end up being inconsistent resulting in "Key not found" exception to be thown. ([#6992](https://github.com/realm/realm-java/issues/6992), since v6.0.16) |
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.
@jedelbo Can you add when that could happen?
If column keys are not unique we end up finding the wrong backlink column during upgrade.
Fixes realm/realm-java#6992