Re: Force Refresh Relation
Re: Force Refresh Relation
- Subject: Re: Force Refresh Relation
- From: Alexander Spohr <email@hidden>
- Date: Thu, 20 Sep 2007 10:41:02 +0200
Am 20.09.2007 um 08:19 schrieb Lachlan Deck:
Hi Alan,
Should I ignore this mail as I am not Alan?
Well put. Would you have any ideas, however, why unless I use
invalidateAllObjects on the shared ec periodically it doesn't pick
up newly inserted objects added by another app into the db, or
indeed forgetting objects that have been marked with isDeleted=true
(which is part of the restricting qualifier)?
Because a shared edcon is considered to hold read-only data anyway?
I'm using a timer to periodically refetch the various entities in
the app into the shared ec. This is not modelled in the eomodel
seeing as there's more than one app using the models. The timestamp
lag is set to around 5 minutes on the shared ec.
Don’t use a shared edcon if you refresh it anyway. Use a new one
instead of refreshing. The refresh renders it useless.
atze
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden