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.
|Published (Last):||14 May 2015|
|PDF File Size:||10.72 Mb|
|ePub File Size:||13.44 Mb|
|Price:||Free* [*Free Regsitration Required]|
Core Data by Marcus S. Zarra
A recent post of his titled Core Data and Deleting Objects set my teeth on edge. We have an initialization, access to the main queue managedObjectContext and a -save method. Marcus has a profound understanding of Core Data, and this book describes not only the basics of working with Core Data, but also how to do so in a performant manner, with explanations and examples. The largest number of Objective-C developers develop only for iOS, and therefore we will keep our focus there.
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. The long history of Core Data has lent itself to different interpretations over the years about how threading should be used, so how should it be done now? About the content This talk was delivered live in October at Pragma Conference.
So, on this line:.
Core Data is not complicated Core Data is as complicated as you make it. The user is the one that should be getting the truth at all times.
Core Data in Swift
The second edition has been substantially updated and the change in emphasis is evident from the change in subtitles of the two editions. The goal of this post is to clear the air about how we should be using Core Data as it stands today, in Jordan will be sorely missed. Recently while using this language feature writing Swift code, I ran into a few snags and learned from the process. This was not such a huge problem as many of the key concepts are valid for both platforms.
This is a case where you can create and conform to a protocol—known in some languages as an interface—to provide a simple way to have each class type provide a display name that can be displayed in your table view controller.
We are now able to at least confirm if we got our threading right or wrong. This Core Data stack will work most of the time.
Now, instead of having a large amount of Core Data code spread dara the Application Delegate and leading to a huge file, we have a very simple and clean object. It writes to disk. ConcurrencyDebug 1 setting when you are running in debug mode.
When you need to deal with more complicated or interesting situations there is a fair chance that Core Data has an advanced feature to handle that situation. If it is going to take time, we do not want to block the main thread and therefore the User Interface.
I can get the data. Ramy Kfoury rated it liked it Aug 22, Learn how to reduce your number of mapping models, integrate your Core Data app with Spotlight and Quick Look, connect your application with sync services, and find out how to use Core Data in a multithreaded environment. Open Preview See a Problem? 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 threading rules were a mess. This book was highly recommended by a couple people I know and it did not disappoint. Until today we had no category for a post like this.