This is because Xcode handles all that by itself. I felt it like a bit of trouble as the auto generated classes don’t have all my properties. So follow these steps to get this as it used to be: Delete what ever classes you already made for core data. Set class.Module as Current Product module … Read more
I was facing something similar with few uses ( by your description I assumed you have way more volume than I do, that’s might the reason for several cases ) In my case Apple seemed to have removed without earlier notice the 20gb free space in the icloud. I noticed that the 2 uses who … Read more
Transformable attributes are useful for storing nonstandard object types within Core Data. For example, I provide code in this answer that lets you store UIImages as an attribute within Core Data. The image data is converted to and from an NSData instance that contains the image’s PNG representation. This is all handled transparently for you … Read more
For what it’s worth, Marcus Zarra seems to be promoting the nil context approach, claiming that it’s expensive to create a new context. For more details, see this answer to a similar question. Update I’m currently using the nil context approach and have encountered something that might be of interest to others. To create a … Read more
If you set the delete rule to “nullify” and delete the A object, then the references to that object in the Bs will be removed. The inverse works the same way. If you have cascade and delete B then it will remove the A that B pointed to. It will then follow the delete rule … Read more
There’s a new section in the sidebar when selecting an entity in the editor for Core Data. You can set what constraint(s) you want to be unique across all instances of an entity For automatic conflict resolution during saves, you’ll need to make sure you’ve got a merge policy set for your managed object context … Read more
The NSManagedObjectContext and any managed objects associated with it should be pinned to a single actor (thread, serialized queue, NSOperationQueue with max concurrency = 1). This pattern is called thread confinement or isolation. There isn’t a great phrase for (thread || serialized queue || NSOperationQueue with max concurrency = 1) so the documentation goes on … Read more
You can do this without leaving Xcode at all (see end of answer for Xcode 4 instructions): Open your data model so it’s visible in the editor pane Single click Classes folder in Group & Pane pane Now single click anywhere in the diagram pane. Press ⌘N to bring up this dialog: Finish the wizard … Read more
I see the same thing, and I consider it to be a bug. It’s not documented anywhere that I can find. Apparently Core Data is applying Objective-C style assumptions here, where a boolean defaults to NO, and an integer defaults to 0. The Core Data/Swift interface has some rough edges, and this is one I … Read more
Since batchupdate is more useful in larger chunks of data, I think this is a more subtle approach. func saveLoginData(accessToken: String, userName: String) { var appDel: AppDelegate = (UIApplication.sharedApplication().delegate as AppDelegate) var context: NSManagedObjectContext = appDel.managedObjectContext! var fetchRequest = NSFetchRequest<NSFetchRequestResult>(entityName: “LoginData”) fetchRequest.predicate = NSPredicate(format: “userName = %@”, userName) if let fetchResults = appDel.managedObjectContext!.executeFetchRequest(fetchRequest, error: nil) … Read more