On 16-jul-2007, at 20:28, 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
>
Perhaps the way that FileMerge works might be an answer?
You'd show the two models side by side or sub-window by sub-window
and show which of the entities overlap one another, then do a test-
delete/merge, then do a re-evaluation that will show what will go
wrong then, and after everything is satisfied, you can do a commit of
some kind.
Does that make sense?
Regards,
Johan Henselmans
http://www.netsense.nl
Tel: +31-20-6267538
Fax: +31-20-6273852
This archive was generated by hypermail 2.0.0 : Tue Jul 17 2007 - 09:02:03 EDT