Re: Problem with EOModeler
Re: Problem with EOModeler
- Subject: Re: Problem with EOModeler
- From: Guido Neitzer <email@hidden>
- Date: Mon, 31 Jul 2006 20:48:52 +0200
On 31.07.2006, at 20:29 Uhr, Chuck Hill wrote:
Yes. I have compared everything, the back relationships too -
everything is the same. They just point to different enttities.
They both use a 24 Byte NSData (bytea) foreign key to connect to
the other entities primary keys.
OK, last guess. :-) Are any of the entities at the destination of
the relationships in an inheritance hierarchy?
Yes, both destination entities are in an inheritance hierarchy. On
the relationship which doesn't get the foreign key contraint is an
abstract "super entity" (I have also tried with a removed abstract
flag) on the other relationship is a non abstract "child entity" the
target.
I have also tried to "re-connect" the relationship (with the target
abstract and a second time with the target not abstract). No change.
I have also tried to create SQL for the whole model or only the
entity I'm interested in. No change. The second foreign key
constraint is not set.
At last I have no created a new entity with the same relationships
with the same result. :-/
I don't know. That's for the myth of having a Java WO app generating
the same SQL as the tools (we had this on the WOLips list today).
Entity Modeler from Eclipse creates both constraints, EOModeler only
one. With the same model.
cug
_______________________________________________
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