I have my old data model, my new model (same but with two more text fields in one ent开发者_运维百科ity) and a mapping model (just the default generated one).
I am getting a strange crash from some of my beta testers that I am having trouble with. The symbolicated crash reports indicate that the crash is occurring in the simple allocation of a controller as
I have a cocoa application using core-data, which is now at the 4th version of its managed object model.
I have Core Data application and I have been migrating (upgrading) the core data model. Each time I create a new version I create a mapping model for each version.
So I created a new version of my data model, and made a previously optional field non-optional (giving it a defau开发者_StackOverflowlt value). According to the documentation, this should mean my migr
I have CoreData-based data layer (using a SQLite datastore) that I am using in both an iOS app and on the server that the iOS clients talk to.The data layer (objc code + coredata model / mapping defns
I have a migration where I\'m moving fields from one entity into another entity which is a child of an abstract entity. My model has an entity, Thing, which is 1->M to an abstract entity, AbstractWidg
I recently tried a lot of different stuff with lightweight migration. These all work: 1) Rename attributes (with renaming identifier specified)
One think I notices is, that I must probably keep the whole stack of model versions intact when shipping updates. I am not sure what happens if someone has version 1.0 with populated data, and then in
I have a deployed app that samples measurements from sensors (e.g., Temp °C, Pressure kPa). The user can create Experiments and collect samples. Each sample is stored as a Run, such that there is a o
加载中,请稍侯......