Databases
StackOverflow2013
Postsdbo
POCore Data Inferred Migration – Automatic "lightweight" vs Manual
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCore Data Inferred Migration – Automatic "lightweight" vs Manual
    primarykey
    data
    text
    <p>I've updated the model of an existing iPhone app in some simple ways (remove attribute, add attribute, remove index), and can use automatic lightweight migration to migrate the persistent store.</p> <p>Due to the typical size of the data set, the processing time is not insignificant, and warrants feedback for the user.</p> <p><code>NSMigrationManager</code> provides a simple but useful <code>migrationProgress</code> value that sends KVO notifications as the migration is performed. That forms the basis of providing feedback, however attempting to use an inferred model (<code>[NSMappingModel inferredMappingModelForSourceModel:destinationModel:error:]</code>) results in drastically different timing for the exact same dataset.</p> <p>Profile results on an original iPhone (2G), Cache size: 1.785 MB on disk.</p> <p><strong>Automatic inferred lightweight migration</strong></p> <pre><code>PROFILE: CacheManager -migrateStore PROFILE: 0.6130 (+0.6130) models loaded PROFILE: 1.1759 (+0.5629) delegate -CacheManagerWillMigrate: PROFILE: 1.2516 (+0.0757) persistent store coordinator loaded PROFILE: 5.1436 (+3.8920) automatic lightweight migration completed PROFILE: 5.5435 (+0.3999) delegate -CacheManagerDidFinishMigration:withError: </code></pre> <p><strong>Manual inferred migration</strong></p> <pre><code>PROFILE: CacheManager -migrateStore PROFILE: 0.6660 (+0.6660) models loaded PROFILE: 1.1471 (+0.4811) inferred mapping model generated PROFILE: 1.4046 (+0.2574) delegate -CacheManagerWillMigrate: PROFILE: 1.5058 (+0.1013) persistent store coordinator loaded PROFILE: 22.6952 (+21.1894) manual migration completed PROFILE: 23.1478 (+0.4525) delegate -CacheManagerDidFinishMigration:withError: </code></pre> <p>So, with an inferred model, the manual migration takes over 5 times longer than automatic!</p> <hr> <p><strong><em>UPDATE: Model loading</em></strong></p> <p>Core Data documentation for <a href="http://developer.apple.com/iphone/library/documentation/Cocoa/Reference/CoreDataFramework/Classes/NSPersistentStoreCoordinator_Class/NSPersistentStoreCoordinator.html" rel="nofollow noreferrer"><code>NSPersistentStoreCoordinator</code></a> <a href="http://developer.apple.com/iphone/library/documentation/Cocoa/Reference/CoreDataFramework/Classes/NSPersistentStoreCoordinator_Class/NSPersistentStoreCoordinator.html#//apple_ref/doc/constant_group/Migration_Options" rel="nofollow noreferrer">"Migration Options"</a> says:</p> <blockquote> <p><code>NSInferMappingModelAutomaticallyOption</code></p> <p>... the coordinator will attempt to infer a mapping model if none can be found.</p> </blockquote> <p>And that is why the XCode built,compiled &amp; bundled mapping model has to be removed (or just un-targetted) to allow an inferred <strong>and</strong> lightweight migration to happen.</p> <hr> <p>It's a big inconsistency, and the <em>lightweight</em> option that <code>NSPersistentStoreCoordinator -addPersistentStoreWithType:configuration:URL:options:error:</code> provides absolutely no indication of progress while processing.</p> <p>Can anybody provide a supported way to get the <code>migrationProgress</code> values during automatic migration, <strong>OR</strong> a way to configure an inferred mapping model to be as fast during manual processing as automatic?</p> <hr> <p><strong><em>UPDATE: Bug Report</em></strong></p> <p>Spoke to the engineers at WWDC and they've asked for a bug report requesting the <code>migrationProgress</code> for the automatic lightweight migration processing.</p> <p>I'll update again if the API is updated to add progress reporting..</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USwestsider
    1. USohhorob
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCore Data Inferred Migration – Automatic "lightweight" vs Manual
      1. USEric Schweichler
      1. VTFavorite
    2. VO
      singulars
      1. POCore Data Inferred Migration – Automatic "lightweight" vs Manual
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POCore Data Inferred Migration – Automatic "lightweight" vs Manual
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload