At 3:55 AM -0700 5/22/08, [EMAIL PROTECTED] wrote:
Il giorno 22/mag/08, alle ore 01:00, Hamish Allan ha scritto:
Do you really need to do this after every object inserted? Could you
do it in bulk?
Not necessarily.
I've tried to do this sequence:
- my second thread add objects into second co
On Thu, May 22, 2008 at 11:37 AM, Dex Morgan <[EMAIL PROTECTED]> wrote:
> What's I'm wrong? The ID still temporany until I save the second managed
> object but If I can do it I can also make my relationship, the overhead it's
> the same.
Surely the overhead is less when you do many rather than on
Il giorno 22/mag/08, alle ore 01:00, Hamish Allan ha scritto:
Do you really need to do this after every object inserted? Could you
do it in bulk?
Not necessarily.
I've tried to do this sequence:
- my second thread add objects into second context until the end
saving each objectID in an arra
On Wed, May 21, 2008 at 11:36 PM, Dex Morgan <[EMAIL PROTECTED]> wrote:
> This link actions happend in the main thread (so inside the main object
> context) and the app can't see objects inserted into the second
> managedobject until I perform a -save: to it.
> However it seems to be a damn expens
Il giorno 22/mag/08, alle ore 00:18, Hamish Allan ha scritto:
Not sure I understand your question, but if you need to differentiate
between objects inserted before some point in time and objects
inserted afterwards, you can explicitly model a timestamp in a managed
object subclass. See e.g.,
ht
On Wed, May 21, 2008 at 9:25 PM, Dex Morgan <[EMAIL PROTECTED]> wrote:
> note: I need to 'see' both
> previous newly inserted object and old objects).
Not sure I understand your question, but if you need to differentiate
between objects inserted before some point in time and objects
inserted afte
