This is a good suggestion. I expect one flaw it does have is if a
change occurs outside the entity you are working with (the updated
methods wouldn't get called). In this situation (with timesheets for a
staff member) I wouldn't expect there to be any external alterations,
however I am also wanting to apply the final solution to another case
where two staff members work in teams and there would be
"interference".
I will add it to my options though.
Ray.
On 4/11/2003, at 6:29 AM, email@hidden wrote:
I've thought about this before, and although I haven't tried it yet, a
trivial solution occured to me. Assuming your filtering/ordering takes
place in _another_ method, which I agree is best, can't you just put
some
cache-invalidating code in the actual relationship manipulation
methods?
I believe that regardless where the change comes from (developer code,
notifications, etc) the relationship manipulation cover methods will be
executed. True?
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
