Default tab "Commit Changes" or "Get Latest"?

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

Default tab "Commit Changes" or "Get Latest"?

Postby david.duffett » Thu Aug 19, 2010 11:19 am

Maybe just for discussion, but would it not be better to have "Get Latest" as the default first tab in SQL Source Control?

I would expect that developers would probably want to get latest version before committing changes, to ensure their changes are compatible with any other changes done in the meantime.

Just a suggestion and perhaps you have better reasons for Commit Changes being the default tab.
david.duffett
 
Posts: 20
Joined: Fri Jul 02, 2010 12:13 pm

Postby slaphead99 » Fri Aug 20, 2010 12:28 pm

I think this seems to be an observation about SQL Source control- right (not SQL Compare)?

But, I think you are right- updating should always be done first. I'll have a chat with the SSC team...
slaphead99
 
Posts: 92
Joined: Wed Mar 10, 2010 2:27 pm

Postby slaphead99 » Tue Aug 24, 2010 8:28 pm

I managed to get some time from our head of UX who explained that the positioning logic was designed with respect to the left-hand panel of SSMS, i.e. the database browser. The logic being that a commit should be adjacent to this panel since it was a local action, whereas an update was more of a remote action. So there's no implication of importance but only physical location. He also said we may review the way source control looks and feels so we are keen on your feedback.
slaphead99
 
Posts: 92
Joined: Wed Mar 10, 2010 2:27 pm


Return to SQL Source Control 1

Who is online

Users browsing this forum: No registered users and 1 guest