-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: API design
-
Labels:None
-
3
-
87
-
Kotlin Beta sprint 14, Kotlin Beta sprint 15, Kotlin Beta sprint 16, Kotlin Beta sprint 17, Kotlin Beta sprint 18
Realm Java right now exposes a manual migration API, while Cocoa/JS/.NET as an almost automatic migration.
Back when these API's where developed we discussed the pros and cons for both approaches. After 3-4 years with both of these API's it is probably safe to conclude that neither negative consequences for these API's have materialized in any meaningful other.
So for the sake of moving fast it is probably easier to expose automatic migration, since that would require less API's from us.
TODO/Questions
- Figure out exactly how migrations should work in Realm Kotlin. What interfaces/API's are needed to support an automatic upgrade process
- If we later decide to re-add support for manual migrations. How can this be done? Ideally it can be done without a breaking change.
- depends on
-
RCORE-967 [C-API] Ability to retrive schema version of a realm
-
- Closed
-
- is depended on by
-
RKOTLIN-141 Story: MVP Automatic Migration support
- Closed