That is one option. Another would be to tell them which models are
in conflict and advise them to create a new model group for each of
these models and use those groups to repair the conflicting names.
Chuck
On Jul 16, 2007, at 11:31 AM, Ken Anderson wrote:
> Text editor :)
>
> On Jul 16, 2007, at 2:28 PM, Mike Schrag wrote:
>
>> Any opinions on what Entity Modeler should do when you load a model
>> group that has two models with conflicting entity names in them?
>> Right now it dies a horrible death, which is obviously undesirable,
>> but the entire state of the model group is really called into
>> question when this happens. You have entire model dependency graphs
>> that can't be resolved no matter what you choose to do, so letting
>> you continue to edit is also sort of dicey. If you can't edit,
>> though, it's possible you can't resolve the conflict, though.
>>
>> I'm open for suggestions ....
>>
>> ms
>>
>
>
--Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects
This archive was generated by hypermail 2.0.0 : Mon Jul 16 2007 - 14:35:29 EDT