Book a Demo

Author Topic: Teamworking: which locking method?  (Read 2669 times)

Matt Thomas

  • EA User
  • **
  • Posts: 29
  • Karma: +0/-0
    • View Profile
Teamworking: which locking method?
« on: August 19, 2011, 08:29:17 pm »
Teamworking: which locking method?Hi All
Searched for similar posts  :)
Using a version control tool that supports file-locking is sufficient for us. However, having just enabled user security, I'm intrigued to know under what circumstances it is more beneficial to use the EA locking method rather than the version control locking method. Clearly, EA's method allows locking of individual elements whereas the version control method does not. So what are the other pros/cons?
Thanks
Matthew

Matt Thomas

  • EA User
  • **
  • Posts: 29
  • Karma: +0/-0
    • View Profile
Re: Teamworking: which locking method?
« Reply #1 on: August 19, 2011, 10:07:35 pm »

Matt Thomas

  • EA User
  • **
  • Posts: 29
  • Karma: +0/-0
    • View Profile
Re: Teamworking: which locking method?
« Reply #2 on: August 19, 2011, 11:16:33 pm »
A more fundamental question is, do we really need locking for most of our model data? See that with a shared model on an e.g. SQL DBMS repository and version control under Subversion, concurrent working within a package by multiple users might not involve frequent merging as long as the users refresh their views.

Please can people shed light on this either theory or shared experience?

I understand that locks are necessary for non-mergeable files, such as bitmaps, etc.