Databases
StackOverflow2013
Postsdbo
POBacking out a Core Data migration?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBacking out a Core Data migration?
    primarykey
    data
    text
    <p>I have an app with a very large Core Data database. I have versioned it many times over the past year.</p> <p>The last time I versioned the database I made one simple change to an entity: I added a new optional attribute. For some reason it would not migrate using Light-weight Migration. I found out much later that this was due to a bug in Apple's Light-weight Migration code resulting from the 'renaming identifiers' that I had needed back in another versioning.</p> <p>Anyway, I digress...</p> <p>Because of the bug that kept me from using Light-weight migration, I created a mapping file to help with the migration, not understanding that this would was a much heavier process and would force my users to wait while the app loaded the entire database into memory while doing the migration. It turns out that this is not really an option at all with very large databases and many of my users were unable to migrate the database at all due to memory problems, etc.</p> <p>So now I want to re-release my app and clear up this problem. The trouble is, some of my users have a database that is somehow marked as being 'in the middle of migrating'. Even with my new code, which gets rid of the mapping file and supports Light-weight migration, users that are in this state, 'in the middle of a migration', don't seem to get reset.</p> <p>What are my options for backing out a migration? - I can detect that I am in this state because there is a '.myDB.sqlite.migrationdestination_41b5a6b5c6e848c462a8480cd24caef3' file in the Documents directory. Deleting this file does not clear up the migration. My guess is that the database is somehow flagged as being in this state, or is already partially migrated. - I can detect this state and then delete the database altogether. But this forces my users to re-download their data.</p> <p>Any Thoughts?</p> <p>Thanks for you help.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USwestsider
    1. UStoofah
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBacking out a Core Data migration?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POBacking out a Core Data migration?
      1. USlearner2010
      1. VTFavorite
    3. VO
      singulars
      1. POBacking out a Core Data migration?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COLet me just say, glad I'm not you.
      singulars
      1. POBacking out a Core Data migration?
      1. USTechZen
 

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