-
Notifications
You must be signed in to change notification settings - Fork 50
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
From which version is not specified #17
Comments
Hi @oonoo,
Yes, migrateToVersion:@"1.1" block: would run once (and only once) for every device if your new version number was @"1.1" (or higher). It doesn't care how the device got to that version (whether by new install, update, etc.)
Yes, this is also true, I think README states that all un-migrated blocks in-between version numbers will be run. I can see how this behavior might be undesirable in certain situations, so if this conflicts with a use case you have, I'd like to hear it to get a better idea of the migration situations people are having. For example, I've thought to add a |
@pwightman, I think it shouldn't run migration blocks at all if their target version is lower that the current app's version. |
@pwightman, Any news with the |
If i need to migrate from lets say 1.0 to 1.1 and i would use your method migrateToVersion:block: with the parameter @"1.1" for the version, than the block would be executed if the current Version is 1.1 no matter if there was an old version installed. And the block would get executed if the app version is higher. For example if the initial install of the user is 2.0 than the block would get executed.
Please correct me if i am wrong.
Best regards.
The text was updated successfully, but these errors were encountered: