Option to Check Out/Lock
When working on an object, we would like to see an option to check-out and/or lock the item it is mapped to in source control. Preferably, we would like this to happen when the item is edited and compiled. Again, this could be an XML config file option of some kind, or an option during check-in to lock the file for the user checking it in.
This has been released in the latest versions of Source Control for Oracle. The upcoming release removes the clutter of locking partitons and lobs which can only be modified with the connecting table object.
-
Leigh commented
1) Yes.
2) Just support the version control feature. (Amended)
3) Shared. -
Leland Roling commented
1. We do use locks for specific files within some of our development projects, although none are database projects.
2. I'm asking you to prevent modifications to a locked out file in TFS. The user can still modify the file on the schema, but if it is locked in TFS -- the changes will not make it to version control. This prevents other developers from modifying a vital object that someone else may be making major changes to. It will also alert the developer that someone else is working on it. All I'm really looking for is the option to lock the file when a check-in occurs.
3. Shared.