• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Snapshot problems SOLVED, FOR REAL, NO JOKE
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Snapshot problems SOLVED, FOR REAL, NO JOKE


  • Subject: Re: Snapshot problems SOLVED, FOR REAL, NO JOKE
  • From: Mike Schrag <email@hidden>
  • Date: Sun, 22 Apr 2007 15:34:03 -0400

The more I think about it, why would you ever need to use a nested editing context instead of a component level peer editing context?
Nested editing context is useful if you want transactions with checkpoints.  Each nested editing context can act like a checkpoint, allowing you to revert, commit, or wander-away-and-ignore each stage without committing the entire transaction.  I have rarely run into the case where I actually need nested over peer and peer is just easier to deal with, but they do occasionally arise.

ms


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Snapshot problems SOLVED, FOR REAL, NO JOKE (From: Steven Mark McCraw <email@hidden>)

  • Prev by Date: Snapshot problems SOLVED, FOR REAL, NO JOKE
  • Next by Date: Re: Snapshot problems SOLVED, FOR REAL, NO JOKE
  • Previous by thread: Snapshot problems SOLVED, FOR REAL, NO JOKE
  • Next by thread: Re: Snapshot problems SOLVED, FOR REAL, NO JOKE
  • Index(es):
    • Date
    • Thread