On Oct 12, 2009, at 4:32 PM, Jon Hull wrote:
I have spent the last 48 hours (re)reading core data docs. My head
is swimming in docs.
Understandable. It's a complicated technology (especially when you
consider its interaction with Bindings).
The short answer is yes, I understand to give each thread it's own
context, but I don't know if it will break without a run loop.
Maybe I'm being dense - a distinct possibility - but I don't get
what you mean by this. It might be good to start a separate (mailing
list) thread with a detailed explanation of what you intend to do.
Yes, although I also read a warning about using these cross-stores
somewhere, so I was thinking of rolling my own.
If I encountered the same warning, I honestly can't remember it. :-)
The core data UUID would probably also be temporary with the way I
am currently creating my objects (because I wouldn't have saved
yet), so I would need something persistent.
I don't think adding a UUID hurts anything, honestly, so if it
simplifies things for you, go for it.
Yes, well it is fairly complex... but it looks like core data is not
a good fit since a basic requirement is that I need it to store
nested arrays of immutable objects and keep the order (I also need
to allow those objects to be inserted at multiple points in the
array). The immutability and the possibility of multiple entries
make an order property unworkable.
Possibly, but you might be pleasantly surprised (not a knowing
hint, just an honest possibility :-)). If you can, try to explain your
needs. Someone might just have a good suggestion (or solid reasons why
not).
--
I.S.
_______________________________________________
Cocoa-dev mailing list ([email protected])
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
