On 31.07.2006, at 21:00 Uhr, Chuck Hill wrote:
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.
Does the abstract super-entity have a table name?
Yes.
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.
No, they don't use the same code to generate SQL. EOModeler uses
some older EOF code (IIRC) as well as code in the EOModeler plugin,
see /Developer/EOMBundles. For example,
PostgresqlPlugIn.EOMplugin. The plugin handles most of the SQL
generation / customization. Which reminds me, I have fixes for the
PostgresPlugIn that need to get back into Wonder...
I know that. I have seen problems like this before.
I think, the quick solution for now is to use the Entity Modeler
(Thanks Mike, yes, I know the solution ... ;-)) to generate my base
script and check whether everything is correctly generated.
But I was curious what EOModeler does ... and why it does this.
cug
_______________________________________________
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]
