What changes can I not make with lightweight migration to Core Data?

I recently tried many different things with easy migration. All these works:

1) Rename attributes (with the specified rename identifier)

2) Add attributes

3) Add a new object + new attribute + inverse relationship to an existing entity

4) delete existing entities + relations to this object


= It almost seems like LM can be dealt with. Did I miss something? When do I get into trouble and need a more sophisticated approach?

+4
source share
1 answer

Dividing one object into two different objects (Person> Child and Adult) will not work with automatic migration.

Applying logic (renaming a parameter based on the condition of another parameter) will not work.

Most major migrations can be handled automatically. Logical solutions require a matching model or custom transition code.

+5
source

Source: https://habr.com/ru/post/1312741/


All Articles