I've been searching around and let me get this straight, every time I change the attributes of my entities, I need to create an entirely new version of my model? I understand that the SQLite database is now out of sync with my data model, but can't I just delete the sql files and re-run my simulator? This is what I've been doing, but it doesn't seem to be working.
Modifying the Core Data Model Requires New Version Every Time?
196 Views Asked by blee908 At
1
There are 1 best solutions below
Related Questions in IOS
- Overlapping UICollectionView in storyboard
- Cannot pod spec lint because of undeclared type errors
- Is the transactionReceipt data present in dataWithContentsOfURL?
- UIWebView Screen Fitting Issue
- ZXingObjC encoding issues
- iOS: None of the valid provisioning profiles allowed the specific entitlements
- How to hide "Now playing url" in control center
- CloudKit: Preventing Duplicate Records
- Slow performance on ipad erasing image
- Swift code with multiple NSDateFormatter - optimization
- iOS 8.3 Safari crashes on input type=file
- TTTTimeIntervalFormatter always returns strings in English
- How do I add multiple in app purchases in Swift Spritekit?
- Setup code for xibs in iOS. -awakFromNb:
- iOS Voice Over only reads out the title of any alert views
Related Questions in CORE-DATA
- Swift code with multiple NSDateFormatter - optimization
- IOS Where To Persist Current User from Back-end
- iCloud Core Data "no document at URL"
- restrict sqlite-wal and sqlite-shm from icloud backup
- Delegate returning nil - Swift
- How to set a core-data attibute to nil, in Swift?
- iOS make task run on background thread Thread safe?
- Calling method on object in NSPredicate with Core Data
- How to get Managed Object context from RestKit 0.20
- Write NSData in NSHomeDirectory
- My app is crashing when I assign the managed object context to a variable
- Fetch unique object based on attribute name from coredata
- NSPredicate filter part of array
- Property 'package_number_7' not found on object of type 'User *' after Lightweight Migration
- Core Data relationship Many-To One
Related Questions in CORE-DATA-MIGRATION
- Issue with Magical Record while migrating into a new Core Data model
- Core-data perform action after lightweight migration
- iOS8.1 Core-Data Lightweight + Heavyweight Migration
- NSEntityMigrationPolicy vs NSEntityMapping
- Core-Data migration half-not-working
- CoreData migration without Model versioning OR reading sqlite wal file
- Transitioning old Datamodel to completely new one (start from scratch and delete everything else)
- iCloud using core data : Facing difficulty to fetch and show old data of live application in current development application
- Fix Core Data Fail
- Core Data Migration Fail
- Modifying the Core Data Model Requires New Version Every Time?
- Disabling iCloud in Core Data (aka migrating persistantstore file to local) in iOS 7
- NSMigrationManager: what is this auto-generated, yet undocumented method?
- What do I do with the mogenerator files that were generated?
- New Core Data model gives error when upgrading
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
You are correct, any changes to the core data model must be made in a new core data model version. You can avoid having to do this for development builds by resetting content and settings in the simulator, or deleting the old app version on a device before installing. For store builds though, you must correctly manage your model versions so that user's will have their persistent store properly migrated to a new store with the new model. Versioning is required so that lightweight migrations can be performed, without you having to write custom migration code. If you don't want to version your model, you are bound to writing code to properly migrate your entities. This can be a lot of work and difficult to maintain, you'd rather use lightweight migration and versioning.