Red Gate forums :: View topic - List of Changes to Commit is Out of Date
Return to www.red-gate.com RSS Feed Available

Search  | Usergroups |  Profile |  Messages |  Log in  Register 
Go to product documentation
SQL Source Control 3
SQL Source Control 3 forum

List of Changes to Commit is Out of Date

Search in SQL Source Control 3 forum
Post new topic   Reply to topic
Jump to:  
Author Message
SnapJag



Joined: 06 Apr 2012
Posts: 3
Location: Salt Lake City

PostPosted: Tue Oct 22, 2013 11:37 pm    Post subject: List of Changes to Commit is Out of Date Reply with quote

I am getting an error message "The list of changes to commit is out of date, so the commit was refused by the server." The fail happens on the Sending Files to Source Control.

SVN 1.8 (TortoiseSVN)
RedGate Source Control 3.4.8, 3.4.10, 3.5.1

How to reproduce
1) Create a new repository folder
2) Commit all items
3) Open the SVN Repo-browser
4) Copy to ... new branch location
5) Backup database from Shared DB location, which has more branch adjustments
6) Restore database to local "dedicated" environment
7) Link new restored database to this branch (Dedicated)
Cool Try to commit, failure

The reason for step 5-6 is because there is another database that my developers are using to develop against a branch; we want to have an SVN branch that matches the new database schema/data set branch. If people need more information about steps and "how" in this scenario, I'll answer; however, I won't answer questions about why (unless it leads to a solution), or I haven't clarified, but I should've been able to describe why enough to provide context.

Any help to get this working, that would be great. Thanks.
_________________
Greg L. Wright
Sr. DBA \ Consultant
snapjag.com
Back to top
View user's profile Send private message MSN Messenger
james.billings



Joined: 16 Jun 2010
Posts: 1144
Location: My desk.

PostPosted: Wed Oct 23, 2013 8:17 pm    Post subject: Reply with quote

OK, I managed to reproduce this in the end. The important part seemed to be in step 5- the further adjustments only triggered the problem when they were a change to an object that had been previously committed.

Once I got the error I could resolve it by going to the Working Base on the newly linked DB (right click the URL on the SQL Source Control setup tab) and pick "Open Working Base"), then right clicking the 'Tables' folder (this will probably work if you just do the parent folder with the random name) then did an SVN Update.
Once I did that, I refreshed the commit tab, tried again, and it went though.

My guess is that the combination of the restored DB along with the "copy" in SVN somehow gets things out of kilter although I'm not sure exactly how yet... any SVN experts?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic All times are GMT + 1 Hour
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group