Auto Commit in a Shared Development Model

A SQL Server Management Studio add-in to source control your database in Subversion or Team Foundation Server.

Moderators: Chris Auckland, David Atkinson, sherr, PhilScrace

Auto Commit in a Shared Development Model

Postby shivanandk » Thu Mar 31, 2011 6:20 pm

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
shivanandk
 
Posts: 2
Joined: Thu Mar 31, 2011 6:15 pm

Postby james.billings » Fri Apr 01, 2011 12:43 pm

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?
james.billings
 
Posts: 1144
Joined: Wed Jun 16, 2010 11:10 am
Location: My desk.

Is it possible in future version as an option

Postby shivanandk » Fri Apr 01, 2011 12:49 pm

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.
shivanandk
 
Posts: 2
Joined: Thu Mar 31, 2011 6:15 pm

Postby james.billings » Fri Apr 01, 2011 12:51 pm

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!
james.billings
 
Posts: 1144
Joined: Wed Jun 16, 2010 11:10 am
Location: My desk.

Postby David Atkinson » Fri Apr 01, 2011 1:13 pm

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
David Atkinson
 
Posts: 1124
Joined: Mon Dec 05, 2005 4:54 pm
Location: Twitter: @dtabase


Return to SQL Source Control 2

Who is online

Users browsing this forum: No registered users and 0 guests