migration path from b54 to post b74#760
Open
krugerk wants to merge 6 commits intobeeminder:masterfrom
Open
Conversation
v2 already contains the migration path - renaming lastModifiedLocal to lastUpdatedLocal and declaring the new columns dueBy and updatedAt
Collaborator
|
I remember getting this lastUpdatedLocal/lastModifiedLocal stuff to migrate properly being a total nightmare. |
the switch to b54 v1 of the beemindermodel meant that the migration tests broken since they were still setting properties which the restored v1 of the db no longer had with the renamingIdentifier in place, coredata can handle the light migrations itself
krugerk
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The current App Store version is 6.7 (54). It contains just 'v1' of the Core Data BeeminderModel. Along the way, v2 and v3 were introduced in code and have not yet been released to the store. They have appeared however in dev (local) and TestFlight builds.
This PR restores v1 to how it was for the 6.7 (54) release and lets v2 (and then v3) take on the migration.
proposes to fix: #759