BTW, I think Project Wonder might have a fix for this bug ...
ERXModelGroup.checkInheritanceRelationship gets wired up
automatically, and it sounds like it MIGHT be a fix for this problem:
/**
* Corrects a strange EOF inheritance issue where if a model gets
loaded and an entity that has children located in
* a different model that hasn't been loaded yet will not be setup
correctly. Specifically when those child entities
* are loaded they will not have their parentEntity relationship set
correctly.
*/
ms
On Dec 15, 2006, at 5:15 AM, Tonny Staunsbrink wrote:
Thanks for the reference.
I tried rearranging the entities (though this particular subentity
was loaded after the super entity - but other subentities was
loaded befure their superentity), but i didn't solve the problem.
The model referencing the inheritance hierarchy is loaded after the
model with the inherticane hierarchy. And with the hand editing of
the index.eomodel file the super entities was loaded before the
subenties. So the fix mentioned in the wicki should be in place.
What really puzzles me is that the error only shows up, when the
models are connection to different databases. If all the data are
in the same dabase, there is no problem. Neither is there at
problem when referencing the leaves of the inheritance hierarchy.
Anyhow, gues I'll have to stop using cross model refences and
implement som other solution. The instability of this worries me
quite a bit.
And yeah, you're right access to the core code, and fix these
issues there would be nice.
The lack of bugfix updates and the being unable to fix these things
myself makes open source alternatives seems more and more
appealing, even though some of them might not have tools like
EOModeller (I, for one, don't find it that buggy ;-) ).
Cheers
Tonny
On Dec 14, 2006, at 7:41 PM, Francis Labrie wrote:
Hi,
Mike Schrag a écrit :
Wow -- that's really ridiculous. I need to take a look at Entity
Modeler and maybe adjust my sort ordering when I write entities
out to implement that workaround for you automatically.
Yeah, that's another crazy bug. Fixing Entity Modeler would
provide a nice automatic work around for entity initialization
order problem, but unfortunately not for model initialization
order problem...
I would really like to get hands on the core EOF code to fix these
damned bugs directly. :-(
On Dec 14, 2006, at 11:12 AM, Francis Labrie wrote:
Tonny Staunsbrink wrote:
[...]
Any input to this will be much appreciated.
BTW: it is single table inheritance and all the entities of the
inheritance hierarchy a placed in the same model (A).
This is a bug in EOF. Check at this reference, I pretty sure
you'll find the rigth solution: <http://en.wikibooks.org/wiki/
Programming:WebObjects/EOF/Using_EOF/
Problems#EOF_fails_to_fetch_or_save_entities_when_not_correctly_ord
ered_in_model>
--
Francis Labrie
Saint-Bruno-de-Montarville, Quebec, Canada
_______________________________________________
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/ts%
40phonofile.dk
This email sent to [EMAIL PROTECTED]
_______________________________________________
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/mschrag%
40mdimension.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
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]
