objectbox / objectbox/objectbox-java
Roadmap/Consideration to keep old data after type migration
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.6k
- Forks
- 311
- PR merge metrics
- No merged PRs in 30d
Description
Is there any roadmap or consideration to keep old data while doing type-migration?
Describe the solution you'd like
Would be nice to keep old data while doing type-migration. Say @Entity has a long field that should be migrated to int. There could be two solutions:
- Automatic migration, if types are not convertible choose the default value provided
- Let the developer do data migration
Describe alternatives you've considered
Currently, there is no alternative because data migration is internal to ObjectBox and developers don't have the flexibility to handle data migration after type-migration
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing type-migration behavior and how ObjectBox currently handles data that no longer matches the entity field type. Done means defining and documenting a concrete approach for preserving old data, either through automatic conversion/defaults or developer-controlled migration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100