Le 08-08-28 à 09:51, Jonathan Ricker a écrit :
On Aug 28, 2008, at 8:25 AM, Jean-François Veillette wrote:
If by "replace the connection dictionary at startup" you mean in
'Application' or something like that, then yes this will cause
problem. I've seen some methods in EOUtilities reloading model,
and thus reloading the connection dictionnary. You should not
replace it at startup but at every model load (via notification,
as what's being done in Wonder for example).
Oh... I set connection dictionary stuff at the end of my App
constructors. What kind of problems could this cause (when would a
model be reloaded?). I am unaware of ever having problems because
of this. Is it critical I look into fixing this?
Yes, you should most likely fix it soon.
This is how we did 4 years ago as well, but one day we realized that
one fetch was going on the dev database (which was an old replica of
the production database).
I do not remember the details, but it was a method in EOUtilities
(like objectsForEntityName or something) that caused us to use the
notification method instead.
- jfv
Thanks,
Jonathan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
