Re: How to avoid expensive fetches in database when setting to-one-relationship

2016-06-06 Thread Jérémy DE ROYER
rab...@icloud.com>>, WebObjects-Dev mailto:webobjects-dev@lists.apple.com>> Subject: Re: How to avoid expensive fetches in database when setting to-one-relationship According to yours posts, it seems that for performance reasons, we have to think twice (or more) before adding a reverse to

Re: How to avoid expensive fetches in database when setting to-one-relationship

2016-06-06 Thread Ken Anderson
gt; > > From: Jérémy DE ROYER > Date: Monday, June 6, 2016 at 8:44 AM > To: Samuel Pelletier > Cc: Chuck Hill , Philippe Rabier , > WebObjects-Dev > Subject: Re: How to avoid expensive fetches in database when setting > to-one-relationship > > According to yo

Re: How to avoid expensive fetches in database when setting to-one-relationship

2016-06-06 Thread Chuck Hill
: Monday, June 6, 2016 at 8:44 AM To: Samuel Pelletier Cc: Chuck Hill , Philippe Rabier , WebObjects-Dev Subject: Re: How to avoid expensive fetches in database when setting to-one-relationship According to yours posts, it seems that for performance reasons, we have to think twice (or more

Re: How to avoid expensive fetches in database when setting to-one-relationship

2016-06-06 Thread Aaron Rosenzweig
t; >>>> That is what I meant by fetching. You need to re-implement those methods. >>>> Change it to do an fetch on Customer where modeTransport == this >>>> >>>> You can still use it to fetch a ModeTransport based on “listOrder contains >>

Re: How to avoid expensive fetches in database when setting to-one-relationship

2016-06-06 Thread Jérémy DE ROYER
ailto:jeremy.dero...@ingencys.net>> Date: Sunday, June 5, 2016 at 3:26 PM To: Chuck Hill mailto:ch...@gevityinc.com>> Cc: WebObjects-Dev mailto:webobjects-dev@lists.apple.com>> Subject: Re: How to avoid expensive fetches in database when setting to-one-relationship What do you m

Re: How to avoid expensive fetches in database when setting to-one-relationship

2016-06-06 Thread Samuel Pelletier
eTransport based on “listOrder contains >> order”. >> Chuck >> >> >> From: Jérémy DE ROYER > <mailto:jeremy.dero...@ingencys.net>> >> Date: Sunday, June 5, 2016 at 3:26 PM >> To: Chuck Hill mailto:ch...@gevityinc.com>> >> C

Re: How to avoid expensive fetches in database when setting to-one-relationship

2016-06-06 Thread Philippe Rabier
mailto:jeremy.dero...@ingencys.net>> >> Date: Sunday, June 5, 2016 at 3:26 PM >> To: Chuck Hill mailto:ch...@gevityinc.com>> >> Cc: WebObjects-Dev > <mailto:webobjects-dev@lists.apple.com>> >> Subject: Re: How to avoid expensive fetches in

Re: How to avoid expensive fetches in database when setting to-one-relationship

2016-06-05 Thread Jérémy DE ROYER
From: Jérémy DE ROYER mailto:jeremy.dero...@ingencys.net>> Date: Sunday, June 5, 2016 at 3:26 PM To: Chuck Hill mailto:ch...@gevityinc.com>> Cc: WebObjects-Dev mailto:webobjects-dev@lists.apple.com>> Subject: Re: How to avoid expensive fetches in database when setting to-one-relati

Re: How to avoid expensive fetches in database when setting to-one-relationship

2016-06-05 Thread Jérémy DE ROYER
odeTransport based on "listOrder contains order". Chuck From: Jérémy DE ROYER mailto:jeremy.dero...@ingencys.net>> Date: Sunday, June 5, 2016 at 3:26 PM To: Chuck Hill mailto:ch...@gevityinc.com>> Cc: WebObjects-Dev mailto:webobjects-dev@lists.apple.com>> Subject: Re: How to

Re: How to avoid expensive fetches in database when setting to-one-relationship

2016-06-05 Thread Chuck Hill
To: Chuck Hill Cc: WebObjects-Dev Subject: Re: How to avoid expensive fetches in database when setting to-one-relationship What do you mean with « you can still use it for fetching » ? I removed the class property for the Customer to Order (but keeped the « listOrder » relationship) When I set

Re: How to avoid expensive fetches in database when setting to-one-relationship

2016-06-05 Thread Jérémy DE ROYER
What do you mean with « you can still use it for fetching » ? I removed the class property for the Customer to Order (but keeped the « listOrder » relationship) When I set the customer to the order, it runs fast. But when I retrieve the orders using the method below : public NSArray listOrde

Re: How to avoid expensive fetches in database when setting to-one-relationship

2016-06-05 Thread Chuck Hill
You can do that, but the generated method won’t work as they depend on it being a class property. You can rewrite them to do fetches From: Jérémy DE ROYER Date: Sunday, June 5, 2016 at 2:03 PM To: Jérémy DE ROYER Cc: Chuck Hill , WebObjects-Dev Subject: Re: How to avoid expensive fetches in

Re: How to avoid expensive fetches in database when setting to-one-relationship

2016-06-05 Thread Jérémy DE ROYER
Maybe removeRelationship(EORelationship relationship) from EOEntity ? Jérémy DE ROYER Le 5 juin 2016 à 22:57, Jérémy DE ROYER mailto:jeremy.dero...@ingencys.net>> a écrit : My first tests with your solution work great ! Is it possible to remove the class property programmaticaly in order to ke

Re: How to avoid expensive fetches in database when setting to-one-relationship

2016-06-05 Thread Jérémy DE ROYER
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 .eog

Re: How to avoid expensive fetches in database when setting to-one-relationship

2016-06-05 Thread Chuck Hill
Remove the “class property” setting for the ModeTransport to Order. You can still use it for fetching. Chuck From: on behalf of Jérémy DE ROYER Date: Sunday, June 5, 2016 at 12:55 PM To: WebObjects-Dev Subject: How to avoid expensive fetches in database when setting to-one-relationship D