• 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: set values in coredata
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: set values in coredata


  • Subject: Re: set values in coredata
  • From: mmalc crawford <email@hidden>
  • Date: Sat, 10 Feb 2007 21:46:49 -0800


On Feb 10, 2007, at 9:33 PM, Brian Todd wrote:

NSFetchRequest *request = [[[NSFetchRequest alloc] init] autorelease];
[request setEntity:dailyValuesEntity];
[request setValue:[NSNumber numberWithInt:100] forKey:@"value"];


Setting the value of a fetch request does not make sense.
The request specifies the entity you're interested in, what features the instances of the entity must have (defined by the predicate), and the order in which you want them returned.


If you want to change property values in a managed object or collection of managed objects, you must first retrieve the those objects and then change the values.

mmalc

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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: 
 >set values in coredata (From: Brian Todd <email@hidden>)
 >Re: set values in coredata (From: mmalc crawford <email@hidden>)
 >Re: set values in coredata (From: Brian Todd <email@hidden>)

  • Prev by Date: Re: set values in coredata
  • Next by Date: Re: Binding a Popup to an Array of Images?
  • Previous by thread: Re: set values in coredata
  • Next by thread: pasteboard issues
  • Index(es):
    • Date
    • Thread