Thanks, Lachlan.
It was connecting to the wrong database, that is the correct database
for the wrong model that was displayed in the relationship inspector.
But pardon my ignorance of a new (to me) tool. My "doh!" moment was
when I discovered that the "remove" button was the same as
EOModeler's "disconnect" button, and once I did that I could edit the
related model.
I still don't know why it got changed, but that particular problem is
now fixed...
Thomas
On 27/07/2007, at 15:51, Lachlan Deck wrote:
>> I have updated Eclipse to 3.2.2, plus any other updates it offered
>> including some Mac Goodies. The Entity Modeler and other WOLips
>> plugins are still the same.
>>
>> The connection dictionary is loaded at run time from the launch
>> arguments, so the dictionary in the model itself shouldn't matter.
>> However, it is valid, because EOModeler can fetch and display the
>> database contents. I'm not sure how else I can verify it.
>
> Except that you said it was connecting to the wrong database - so
> perhaps your dictionary is not being applied at launch time as you
> thought.
>
>> I have tried Chuck's suggestion of a model group.
>>
>> All of this has not changed the problem with the missing models. I
>> know that Entity Modeler knows about the other models because it
>> checks the others for validity when opening one model.
>>
>> I have set up a brand new project with two models created in
>> Entity Modeler, and the cross-model relationship is working. I now
>> realise that at one stage this was also working in my migrated
>> framework.
>
> Fair enough. Tiring as it may be it might be worth doing 'em fresh
> in Entity Modeler. There might be some left over stuff in there
> that's confusing things.
This archive was generated by hypermail 2.0.0 : Fri Jul 27 2007 - 02:27:37 EDT