On Jul 28, 2009, at 5:36 PM, Jerry Krinock wrote:
But for restoring previous state over an existing object, that's
undesirable. There are other more complicated approaches, but
ultimately handling NSNull in your restore code is the least bad
approach.
In what practical situation would
On 2009 Jul 28, at 16:07, Ben Trumbull wrote:
Accessor methods don't accept NSNull in place of NSString.
Yes.
I think I understand this now -- I was having trouble with your terms
"copy/snapshot" and "restore".
Accessor methods don't accept NSNull...the swapping has to happen in
your c
On Jul 28, 2009, at 3:59 PM, Jerry Krinock wrote:
Last December I asked a question here regarding how I should copy
attributes from an existing managed object to a new managed object,
when it is necessary to create this new object in a different
managed object context. I noted that gettin
Last December I asked a question here regarding how I should copy
attributes from an existing managed object to a new managed object,
when it is necessary to create this new object in a different managed
object context. I noted that getting an "attributes dictionary" from
the existing mana
My app maintains in its managed object context an array of, say,
Potato objects. The potatoes in this central managed object context
come and go occasionally -- someone might throw in a new one, or eat
one. An archived potato is low in calories, consisting of a half
dozen numbers or short string
On Sat, Dec 20, 2008 at 9:29 PM, Jerry Krinock wrote:
> Both. The app-wide MOC has its PSC set to the app-wide PSC, which in turn
> has a persistent store in the Application Support folder.
OK, good, glad I understood you there.
> By UUID, I believe you mean [[[self objectID] URIRepresentation]
I am doing something very similar to you. I have an application-based
library of potatoes, and each document has a copy of some of those
potatoes. I did this because the document may be opened on another
computer that does not have access to the same library (or as you
mention, the library
On 2008 Dec, 20, at 17:55, Kyle Sluder wrote:
This doesn't make sense... you don't store arrays in managed object
contexts.
Whoops. Indeed, that does not make sense. I should have said that
there are potatoes inserted into the app's central managed object
context. They're not in an arr
On Sat, Dec 20, 2008 at 6:58 PM, Jerry Krinock wrote:
> My app maintains in its managed object context an array of, say, Potato
> objects. The potatoes in this central managed object context come and go
> occasionally -- someone might throw in a new one, or eat one. An archived
> potato is low i
My app maintains in its managed object context an array of, say,
Potato objects. The potatoes in this central managed object context
come and go occasionally -- someone might throw in a new one, or eat
one. An archived potato is low in calories, consisting of a half
dozen numbers or short
10 matches
Mail list logo
