Working with shared model

[EA2412]

Hello everybody,

I´m working in a company trying to use EA with the shared model as a version control deployment schema. First I was setting up a server working with MySQL as DBMS network server. The network server for the version control was already existing. Now 10 people are working on the same model which I load up to the MySQL server. My question is: is there a "real time" connection to the DBMS on each client who sets up an ODBC connection by starting EA? So- do they work on the latest version automatically by starting EA or do they have to load the actual model version from the network server on their own?

Thanks a lot for your help
EA2412

[«Midnight»]

No, it is not real time in the sense you are using. EA uses a different, but workable, paradigm.

Check the White Papers page in the Resources section of the Sparx site for a guide on using version control with EA.

[Eve]

Just to clarify a little what I think David meant.

If you're using version control in a shared repository you are working directly on the DBMS.  You will not see changes other users make 'instantly' as there have been a few posts about recently, but when EA reloads that part of the model.

For example, if another user moves something on a diagram (and saves the change), you will see the change when you next load the diagram.  If another user changes a class name that name will be updated on diagrams when you load the diagram, in the properties dialog when you open it, and in the project browser only when you reload the relevant branch of the model.

[RoyC]

Reloading the model (or diagram) is very quick and easy. In the product Help (the one you get from the EA toolbar, not the version on the web) there is a small topic on the several methods for refreshing your model to display recent changes. Look at Model Management | Version Control | Use Version Control | Refresh View of Shared Product.

[johnm9]

After talking so much about shared repository and import and export and this guide and that guide, making it simple, EA does not provide concurrent editing of models functionality as what cvs does to codes. right?

Atmost, it supports shared model in the sense that we have a shared place to hold the model. We can modified that model. But NO concurrent editing of same model element and then EA identifies you those conflicting modifications since last checkin version.

=> Same model element can only modified by only one user at a time.

Please don't beat around again. If i'm wrong, point me to the exact steps where EA will list me those conflicting point.

[RoyC]

Not sure why you are posting in this thread - the issue you are talking about is not the same thing that EA4212 wanted help with. We have responded to his questions.

For the record, you are right - you cannot do what you want to do. Not directly, anyway.  As Simon says in your other thread, you can get around it by taking Baselines of your changed packages before checking them in, and then rolling back the preferred changes from one or other of those. If this sounds useful to you and you want more details, just ask.

[«Midnight»]

And yes Simon, that's what I was trying to get at. Thanks for clarifying this. I didn't want to go into more detail in case anything had changed in build 831; I've not yet had time to look.

David