-
Type: Task
-
Resolution: Duplicate
-
Priority: Unknown
-
None
-
Affects Version/s: None
-
Component/s: None
Problem
Example:
- I have a realm schema for an object Person.
- Person has a field birthDate: Int in v1
- In v2, schema has changed to birthDate: RealmInstant
Opening Realm instance with new schema and old realm file does not cause exception.
Exception is thrown at runtime, when I actually try to query for the row.
This is different from Java SDK where it caused exception on startup.
Solution
Not sure. Maybe checking that migration had happen for fields that changed type (or were changed in different way that cannot auto migrate)
Alternatives
No response
How important is this improvement for you?
Would be a major improvement
Feature would mainly be used with
Local Database only