• 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: Ordered Sets and NSManagedObjectID
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Ordered Sets and NSManagedObjectID


  • Subject: Re: Ordered Sets and NSManagedObjectID
  • From: Robert McNally <email@hidden>
  • Date: Sun, 15 May 2005 22:36:03 -0700

Malcom,

Thanks for your response. I apologize if the pertinent details were buried too deeply in my original message, but I am already aware of -URIRepresentation. The specific questions are:

1) Are the *temporary* URIs that -URIRepresentation returns for objects that have not yet been committed eligible for archiving, for example as an NSString property on a separate NSManagedObject-- or must the object a URI represents first be saved to the underlying store before they can be archived using the "permanent" URI returned thereafter?

2) Can the NSURL returned by -URIRepresentation only be archived by using NSCoding, or will the NSString method I mention work, or is there some other recommended way of archiving the URIs?

3) If *temporary* URIs cannot make the round trip and still be meaningful in a later execution context, is there some way to force the persistence stack to assign a proper *permanent* URI to particular managed objects *before* saving, so other objects can use the permanent URIs within their own attributes? Recall that the reason I want to do this is so I can use the *order* of the URIs in an NSString property to preserve the order of a to-many relationship.

Thanks,

Robert

>On May 14, 2005, at 9:02 PM, Robert McNally wrote:
>
>>The first issue is: the documentation says that NSManagedObjectIDs "can be archived and recreated later to refer back to a given object." But it does not give any hints as to the "right" way to perform the archiving.
>>
>
>- (NSURL *)URIRepresentation
>Returns a URI that provides an archivable reference to the object which this ID represents.
>
>
>The Class Description will be made more explicit anon...
>
>mmalc


--
______________________________________________________________________
Robert McNally, Arciem Engineering             <http://www.arciem.com>
                                                          626/963-7760
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Ordered Sets and NSManagedObjectID
      • From: mmalcolm crawford <email@hidden>
References: 
 >Ordered Sets and NSManagedObjectID (From: Robert McNally <email@hidden>)
 >Re: Ordered Sets and NSManagedObjectID (From: mmalcolm crawford <email@hidden>)

  • Prev by Date: Re: FSCopyObjectAsync: useless and crippled
  • Next by Date: Re: Binding to an array.name, how?
  • Previous by thread: Re: Ordered Sets and NSManagedObjectID
  • Next by thread: Re: Ordered Sets and NSManagedObjectID
  • Index(es):
    • Date
    • Thread