Auto Commit in a Shared Development Model

shivanandk · March 31, 2011 1:20PM

Hi,

Is it possible to set to auto commit the changes from database version to Source control, whenever a developer makes changes in the database ?

Thanks,

Shiv Kamath

James B · April 1, 2011 7:43AM

This isn't currently possible - the commits only happen when you visit the commit tab and choose to actually execute the process.

I'd imagine it could potentially be a dangerous operation; if a developer is working on something that involves changes to several objects then each one being committed automatically at various intervals could lead to strange behaviour or conflict with work other developers are doing?

shivanandk · April 1, 2011 7:49AM

Is it possible in future version as an option or setting that allows auto-commit. This will be very useful for small developer team (2 to 5 people). The developer often forgets to commit the changes to the source control.
I do not want auto commit on the other way (from source control to database) as it would be not good option.

James B · April 1, 2011 7:51AM

I don't think it's currently planned as a feature, however could I ask you to check and post it on our Uservoice - see here

Then other users who want this option can vote it up, increasing the chances we'll implement it!

David Atkinson · April 1, 2011 8:13AM

One problem with this feature is that it would make it easy for breaking changes to be committed.

There are other undesired changes that could happen. For example, if a developer accidentally commits a change that deletes data, and another developer assumes the change is good and gets it, this would have very undesirable consequences.

What are your thoughts on these side effects?

David Atkinson
Product Manager
Red Gate Software

Auto Commit in a Shared Development Model

Comments

Product Learning

Community Forums

Events & Friends

Simple Talk