• 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: NSUndoManager f@*#ing up Core Data database
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSUndoManager f@*#ing up Core Data database


  • Subject: Re: NSUndoManager f@*#ing up Core Data database
  • From: Ruotger Skupin <email@hidden>
  • Date: Thu, 9 Oct 2008 12:10:13 +0200

Hi Ben,

yes, there are some sporadic problems left in save: but these are exception I can handle. The NSUndoManager crashes were totally beyond my control, so this is going to help a lot.

Thanks
	Ruotger


Am 08.10.2008 um 22:23 schrieb Ben Trumbull:

Ruotger,

This has less to do with the undo manager itself, and more to do with event coalescing. You can set the undo manager for the MOC to nil, but this problem will happen elsewhere later, like -save: or - executeFetchRequest: or when you call -processPendingChanges yourself. This code is following the delete rules in your model for a deleted object to cascade the necessary relationship maintenance throughout the graph.

- Ben


_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >re: NSUndoManager f@*#ing up Core Data database (From: Ben Trumbull <email@hidden>)

  • Prev by Date: Re: Just when I thought I understood bindings.
  • Next by Date: Re: NSUndoManager messing up Core Data database
  • Previous by thread: re: NSUndoManager f@*#ing up Core Data database
  • Next by thread: refreshObject doesn't seem to work
  • Index(es):
    • Date
    • Thread