iphone - Which kind of changes can't I do with lightweight migration in Core Data? -


I recently tried many different things with light migration. All these functions:

1) Rename attributes (with the change of name of the identifier) ​​

2) Add attributes

3) New unit + new feature + Add inverse relationships to the already existing entity

4) Remove the existing unit + the relationship in that unit


= It almost looks like almost anything with LM can handle. Did I forget something? In which case I am having trouble and need some more complex approach?

Divide an entity into two separate entities (person> child and adult) of automatic migration I will not work with.

Applying the argument (changing the name of a parameter based on the status of another parameter) will not work.

Most of your original migrations can be controlled automatically. Mapping model or custom migration code is required to deal with logic decisions.


Comments

Popular posts from this blog

windows - Heroku throws SQLITE3 Read only exception -

lex - Building a lexical Analyzer in Java -

python - rename keys in a dictionary -