When I imported my model from EOModeler to Entity Modeler it gave me a
warning about some relationship names starting with capital letters. I
renamed them to start with lower case letters, but this broke any
flattened relationships based on them. I am sure EOModeler used to
propogate relationship name changes through the definition of flattened
relationships, so this caught me by surprise. If you are renaming
relationships you might be creating a similar situation.
Tim
Quoting Thomas <webobject..oomeranet.com.au>:
> I've made great progress in migrating my framework to Eclipse. I've
>
> reduced the number of errors from over 10,000 to zero.
>
> 8^)
>
> However I have another problem. The application using the framework
>
> runs OK as long as I don't edit the relationships in Entity Modeler.
>
> I have five different EO Models, with a number of cross-model
> relationships. When I view the relationship in Entity Modeler
> (regardless of whether I have both models open, or even have the
> project open in XCode), the "Model" popup menu in Entity Modeler is
>
> greyed out, showing the current model instead of the other model, and
>
> I can't change it. The Destination popup is grey and empty. If I save
>
> this model from Entity Modeler, the application fails on fetching the
>
> related objects because the SQL generated is looking in the wrong
> database. If I then edit the model in EOModeler and save it, the
> application works.
>
> My Googling suggests that there should be no problem with cross-model
>
> relationships. I have Eclipse version 3.2.1 and the WOLips plugins
> are mostly 2.0.0.4061.
>
> Any hints would be appreciated.
>
> Thomas
>
>
>
This archive was generated by hypermail 2.0.0 : Fri Jul 27 2007 - 02:08:35 EDT