Book a Demo

Author Topic: Loss of references when using several databases  (Read 4446 times)

GBeutler

  • EA User
  • **
  • Posts: 23
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Loss of references when using several databases
« on: June 05, 2008, 08:16:15 pm »
Hi All,

Part on , the problem:
We use EA with databases and SVN. The databases are project related and have some common modules i.e. actors and a common service layer etc. I ran in the following problem:

Step 1:
Project DB A:
checkout on the common actors.
checkout the local use cases of Project A

change some associations of the use case model.
commit everything.

Step 2:
Then I switch to Project database B. The actors are from the same SVN but the use cases of project A do not exists in the project B model.

checkout the common actors
modify i.e. a comment of a actor.
commit the actor.

Step 3:
Go back to project model A
checkout the common actors which were changed in step 2.

Result:
The associations which were added in step 1 are lost.

Reason why working with different project databases:
I can not exclude read access to packages for users. We have i.e. requirements at the model(s) which are not public for everybody. I can restrict nearly everything by using the EA user concept but not the read access to packages and their content. Maybe I am wrong but I wasn't able to finde a oppotunity tho configure this. So we decided to spread our model over several databases and "meet" at the SVN with our changes. Looks like this don't work for us.

Has somebody seen this before? We will now update to 7.1 (comming form 7.0.817) and test if the issue still exists but I think this is a general problem.

thanks in advance and best regards,

Guido