Re: How to avoid expensive fetches in database when setting to-one-relationship
Re: How to avoid expensive fetches in database when setting to-one-relationship
- Subject: Re: How to avoid expensive fetches in database when setting to-one-relationship
- From: Jérémy DE ROYER <email@hidden>
- Date: Sun, 05 Jun 2016 20:57:04 +0000
- Thread-topic: How to avoid expensive fetches in database when setting to-one-relationship
|
My first tests with your solution work great !
Is it possible to remove the class property programmaticaly in order to keep the generated .eogen (and all the associated methods) up and running ?
Or maybe another « practical » solution better than re-add the properties before generating the .eogen and our associated .class and then removing the properties.
Remove the “class property” setting for the ModeTransport to Order. You can still use it for fetching.
Chuck
Dear all,
In our app, we have a one to many relationship between order and mode transport
For each order, we set the mode transport using the method below :
public void setModeTransportRelationship(ModeTransport
value) {
if (_CommandeClient.LOG.isDebugEnabled())
{
_CommandeClient.LOG.debug("updating modeTransport from " +
modeTransport() + " to " + value);
ModeTransport oldValue = modeTransport();
removeObjectFromBothSidesOfRelationshipWithKey(oldValue, "modeTransport");
addObjectToBothSidesOfRelationshipWithKey(value, "modeTransport");
Then, an objectWillChange() is fired for the mode transport… but the (not wished) consequence is that every to many relationships from the mode transport are fetched (even if we don’t call the associated method for the mode transport). However,
the objects associated with the to one relationships are not fetched.
We observed the same behavior for the customer object when using the setCustomerRelationship method of the ordre. The (bigger) problem is that the customer object has dozen of to many relationships... fetched for nothing…
At the beginning we had few orders but now, we have to wait from 10 to 30 seconds until de saveChange is ended and that’s really not effective. More than 90 % of this time is spent for fetching the to many relationship whereas we just had to save the order
values...
Any idea how to deal with theses not-wished-fetches ?
|
_______________________________________________
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