Book a Demo

Author Topic: SVN and Database  (Read 3996 times)

RedMoomba

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
SVN and Database
« on: April 24, 2008, 05:10:26 am »
Have a question about using version control and database upsizing. And I just want to clairify.  I definitely want to use SVN and have version control capabilities. So the way I think is the EAP project will be kept in SVN. But I would also like to keep my EAP in a database.

Is this a question of either/or  Either you have SVN Version Control or you can keep your EAP project in a database, but not both?

Thanks

Krzysztof Swiatkowski

  • EA User
  • **
  • Posts: 76
  • Karma: +0/-0
  • Understanding is a three-edged sword
    • View Profile
Re: SVN and Database
« Reply #1 on: April 24, 2008, 07:17:16 am »
If I understood you correctly you want to keep your project in either EAP-File or SQL-database. I don't think it has anything to do with versioning. You will need to version control packages of your project and it will not matter where the project is kept. Define VCS in EA, and add project to VCS by r-clicking on a model and select Package Control>Add branch to version control.
Read help on the subject. EA 7.1 makes it easier to version a project.

Regards
Kris
If I put you finger in the eye
then you have finger in the eye
and I have finger in the eye
but it's not the same

mrf

  • EA User
  • **
  • Posts: 311
  • Karma: +0/-0
    • View Profile
Re: SVN and Database
« Reply #2 on: April 24, 2008, 08:22:47 am »
Hello,

As Kris stated, version control is agnostic to how the model is stored. Version control isn't necessarily a storage mechanism, but more a facility that allows you to share packages between multiple repositories (be they EAP or SQL) in a controlled fashion.

Best Regards,

Michael

[email protected]
"It is more complicated than you think." - RFC 1925, Section 2.8

Martin Terreni

  • EA User
  • **
  • Posts: 672
  • Karma: +0/-0
  • Sorry, I can't write
    • View Profile
Re: SVN and Database
« Reply #3 on: April 26, 2008, 04:30:44 am »
We use MSSQL as repository and VSS for VC and it works fine together.
Recursion definition:
If you don’t understand the definition read "Recursion definition".

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: SVN and Database
« Reply #4 on: April 28, 2008, 04:59:18 pm »
That seems to be a common misunderstanding. I've had a number of questions about this topic when trying to explain the setup of an enterprise EA on a dbms using version control.
Actually it is quite simple.
- The model is stored on the database.
- Users work directly on the database.
- As a result the other users can see changes immediately, so they don't have to wait for a check-in to see certain changes.
- VC works with exporting/importing xmi files.
- In you version control system you don't have the database, you have the xmi files.
- If a user has a certain packages checked-out, this package is locked so that only this user can change it.
- If a user check in a package then the contents of the package gets exported to xmi, uploaded to the VC-system, and the lock is released.

Hope this clarifies things a little.

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: SVN and Database
« Reply #5 on: April 29, 2008, 09:51:44 am »
Just a clarification of the word immediately from Geert's very helpful post.

Other users will see the changes next time the data is loaded.  This could be opening a diagram, reloading the project, the project browser or part of it.

mrf

  • EA User
  • **
  • Posts: 311
  • Karma: +0/-0
    • View Profile
Re: SVN and Database
« Reply #6 on: April 29, 2008, 01:53:50 pm »
There is a guide to Version Control within Enterprise Architect availble from the whitepapers section of the Sparx Systems website at http://www.sparxsystems.com/WhitePapers/Version_Control.pdf

It may be well worth a read if you require further clarification.
Best Regards,

Michael

[email protected]
"It is more complicated than you think." - RFC 1925, Section 2.8