Re: ordered and filtered fault efficiency
Re: ordered and filtered fault efficiency
- Subject: Re: ordered and filtered fault efficiency
- From: OC <email@hidden>
- Date: Sun, 15 Feb 2015 09:50:06 +0100
P.S.
On 15. 2. 2015, at 9:19, OC <email@hidden> wrote:
>>> and it is a must to speed up lastValidPriceOffer -- very considerably, preferrably to O(1) if possible.
>> I’d model a to-one and update this when the priceOffers relationship changes.
>
> Hmmm... actually, does this differ anyhow from caching the GID? (Save for the first access, for cached GID is not stored in the DB, and thus forces search once.)
At the second though, I can see lots of reasons how does this differ -- e.g., it gets synced betw ECs intra- and with remote synchronizer also inter-instance, which the cache would not be.
Hmmmm....
> That aside, for this app it is somewhat inconvenient to change the DB schema. For the next release I will do that.
... perhaps I try to find a way to do it for the current release, too :)
Thanks a very big lot,
OC
_______________________________________________
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