[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Partially saving the object graph. How?

Subject: Re: Partially saving the object graph. How?
From: Jean Pierre Malrieu <email@hidden>
Date: Mon, 19 Mar 2007 20:42:09 +0100
Delivered-to: email@hidden
Delivered-to: email@hidden

Jean,

I think it might be easier if you gave us a more specific context for
what you're doing. This need doesn't make a lot of sense to me. If we
knew why that were necessary, we might be able to help you think of a
better solution. :-)

It's a pretty general question, and others might have faced this requirement... I don't abolutely rely on this design. Right now, I don't use it. But that would be very convenient to me: less components to manage, and better user experience.


That having been said, I think you might be able to override
updatedObjects(), insertedObjects(), and deletedObjects(), and filter
the results from those to include only objects that are instanceof A.
That strikes me as the method involving the least amount of work, but
I'm not sure what the results of that would actually be once it
filtered up to  saveChanges(). I suspect at that point, it might
ignore those accessors, but you could try it.


Thanks. That's an idea. I'll see if it is feasible.

JPM
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/email@hidden

This email sent to email@hidden

Follow-Ups:
- Re: Partially saving the object graph. How?
  - From: Chuck Hill <email@hidden>

Prev by Date: Re: Partially saving the object graph. How? (Jean Pierre Malrieu)
Next by Date: Re: Partially saving the object graph. How?
Previous by thread: Re: Partially saving the object graph. How?
Next by thread: Re: Partially saving the object graph. How?
Index(es):
- Date
- Thread

Home