Mar 22 2020

The first edition of Core Data by Marcus Zarra was the book I turned to when I wanted to learn Core Data. Whilst it is still a great book it was. Threading in today’s Core Data is radically different from its original In this talk from #Pragma Conference , Marcus Zarra presents the. Core Data in Swift. by Marcus S. Zarra. Publisher: Pragmatic Bookshelf. Release Date: June ISBN: View table of contents. Start reading.

Author: Gak Vudoktilar
Country: Malta
Language: English (Spanish)
Genre: Photos
Published (Last): 19 April 2010
Pages: 396
PDF File Size: 13.38 Mb
ePub File Size: 16.7 Mb
ISBN: 835-1-58540-766-4
Downloads: 52708
Price: Free* [*Free Regsitration Required]
Uploader: Makree

Most of the time you do not need zrara want the advanced features of Core Data and can just grab an instance of NSPersistentContainer and be happy. While at Empirical Development and then MartianCraft I had been distanced from all of the inventive solutions that other development karcus have been coming up with for the past few years. The SQLite is transparent. On the other hand if you have been using Core Data for a while you can jump straight to the chapters on migrations, performance and threading and learn something.

Jon Ensminger rated it really liked it Dec dafa, It deserves a proper controller of its own. I purchased the 12 inch MacBook. Ask me again in a year, I might change my mind. Use them once, then throw them away. If you like books and love to build cool products, we may be looking for you.

Core Data in Swift

Contact me ; we can discuss the options. Marcus does mention the problems Apple has had getting this to work reliably:.

The goal of this post is to clear the air about how we should be using Core Data as it stands today, in Yet the Core Data stack initialization code is still the same. Any non-user work importing and exporting should be done on a child context on a background thread see response to 6 above. It could be a red herring. And if you want to just cut to the chase, grab the code from github.


No disagreement; Core Data is your object model and it can persist cor a database but that is not its biggest strength. In my playing and working with Realm, I find that the amount of code you write is datx equal.

Firstly because you should realise that you already know much of what is required. When you access the application delegate in this way you are effectively promoting its properties to the status of global variables and singletons.

May 06, Wai Lam rated it it was amazing. Shortly after my acceptance I had heard that there was some controversy surrounding the conference about a comment made by one of the organizers who had attended another conference. The first half of the book provides an in depth coverage of the key concepts of Core Data. If it is going to take time, we do not want to block rata main thread and therefore the User Interface. The next three chapters on Core Data cpre and migration, performance tuning and threading are all essential reading.

If debugging is that hard, why would we ever want to write code at the edge of our ability? Such a simple and yet vital job in the application. This is a very common problem in the little startups. The response to that request might be instances of NSManagedObject or might be an NSFetchedResultsController which then serves up the data objects in a xata and reliable way.

What, though, is the safe Swift way of handling this? Marcus does mention the problems Apple has ,arcus getting this to work reliably: That is the area of using Core Data in a multi-threaded environment. Keep the code simple. The idea here is that the Application Delegate will call this controller right away.

Do it right and it will be easy to zxrra. The storage is opaque, for instance, and that make me little jittery. The user is the one that should be getting the truth at all times.

My Core Data Stack

They are cheap and meant to be thrown away after a single use. Books by Marcus S.

This is a rare situation since we test completely, right? One of the problems with dealing with a framework that old is that there are eleven years of blogs and articles talking about Core Data, some of which zatra no longer accurate.


The User Interface is designed to run on a single thread and therefore using additional NSManagedObjectContext instances is unnecessary and creates problems. The focus of my talks for is the Core Data stack. It had, in my opinion, a lot to do with the huge influx of developers that we got. Zzarra you like a fresh madcus of eyes on your project to get an idea of where things are? Notice we also have an address property that points to a dictionary.

NSManagedObject instances are your data objects and should be treated as such. It focuses on Swift and adds an additional chapter on how to dwta Core Data with an efficient network implementation, with best practices on how to zarta and pre-load data into your Swift application.

If you start, you tend to get a little bit overanxious and start listening to the notifications all over the place. Unfortunately, as has been demonstrated numerous times in the past, syncing is hard, very hard. Taught at universities around the United States Spoken at nearly every Apple related tech conference around the world Provided workshops on persistence, Core Data and Networking at many conferences and large corporations in and around the United States.

If the user is going to edit something, we use this context.

Core Data by Marcus S. Zarra

Jaime rated it it was amazing Sep 20, The answer usually revolves around a performance problem. They can be messy that way. Given an array of dictionaries like this, you can see how that is providing pretty much what we used to get from valueForKeyPath:.