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
This archive was generated by hypermail 2.0.0 : Mon Jul 16 2007 - 14:29:50 EDT