Database Reference
In-Depth Information
But behind the scenes, by using a child context as a container for edits to a journal
entry, you've reduced the complexity of your app's architecture. With the edits on a
separate context, cancelling or saving managed object changes is trivial.
Nice work, dude! You're no longer a kook when it comes to multiple managed
object contexts. Bodacious!
Where to go from here?
If you followed this chapter all the way through, you've turned an app with a single
managed object context into an app with multiple contexts. You'll find the final
project for this chapter in the
SurfJournal-Final
folder.
First, you improved UI responsiveness by performing the export operation on a
managed object context with a private queue.
Next, you improved the app's architecture by creating a child context and using it
like a scratch pad.
You also learned how to talk like a surfer. That's a good day's work!
Challenge
With your newfound knowledge, try to update
“SegueListToDetailAdd”
so that it
also utilizes a child context when adding a new journal entry.
