ios - Core Data Mapping Model version hashes not matching to source model version hashes -


with core data migration debug enabled, when performing migration see 3 entities (2, 3, 4) changed hashes, expected. entity 1 doesn't change , illustration.

store metadata (source model):

entity1 = <67852e01 ...>;  entity2 = <2b68bba5 ...>;  entity3 = <58babd8d ...>;  entity4 = <1c694c80 ...>; 

current model (destination model):

entity1 = <67852e01 ...>;  entity2 = <260e4d68 ...>; entity3 = <13360b6f ...>;  entity4 = <16513e1b ...>; 

next, create mapping model, hashes in mapping model different in actual models:

mapping model source hashes:

entity1 = <67852e01 ...>;  entity2 = <2b68bba5 ...>;  entity3 = <d66bed18 ...>; // !!! entity4 = <2c56997a ...>; // !!! 

mapping model destination hashes:

entity1 = <67852e01 ...>;  entity2 = <260e4d68 ...>;  entity3 = <cb08343c ...>; // !!! entity4 = <1bc2cf8c ...>; // !!! 

what reasons mapping model created different hashes actual store's hashes? looked @ question , tried updating mapping model's models, didn't work.

the solution worked create new model version in entities removed, create new model, entities re-introduced.


Comments

Popular posts from this blog

java - Play! framework 2.0: How to display multiple image? -

gmail - Is there any documentation for read-only access to the Google Contacts API? -

php - Controller/JToolBar not working in Joomla 2.5 -