Get Latest does not "force column order"

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

Get Latest does not "force column order"

Postby geno.prida » Thu Nov 04, 2010 8:08 pm

Is there any way to force column order when doing a Get Latest?

Also, is there anyway to have custom filters like SQL Compare?
geno.prida
 
Posts: 2
Joined: Tue Jan 30, 2007 11:35 pm

Postby David Atkinson » Fri Nov 05, 2010 7:04 am

Is it important that your column order is sync'ed when getting from source control? We'd definitely consider changing this behavior if others believe that this is the right thing to do. Please join the debate!

Regarding filtering, we're working on specifying this feature now. Could you please describe which objects you'd like to filter out. Would you like to filter these objects so they never reach source control, or would you just want to exclude them from the commit list?

Kind regards,

David Atkinson
Red Gate Software
David Atkinson
 
Posts: 1124
Joined: Mon Dec 05, 2005 4:54 pm
Location: Twitter: @dtabase

Postby MartinU » Wed Feb 09, 2011 4:51 pm

We are currently evaluating SQL Source Control for a move from Visual Studio DB projects. I would say this is a very important aspect of deploying the source.

We have several databases with some being very large in number of objects and it is very important to our organization that we are working from the exact code that is to be released.

Additionally, if you don't have a mirror image of the source controlled code do you really have the "latest"?
MartinU
 
Posts: 13
Joined: Wed Feb 09, 2011 4:43 pm

Postby David Atkinson » Sat Feb 12, 2011 6:39 pm

We take your point that in a development environment, such as one that SQL Source Control is used with, the column ordering should be considered a difference. We've adding this change of behavior to our backlog.

Thanks for highlighting this to us! Keep the feedback coming.

David
David Atkinson
 
Posts: 1124
Joined: Mon Dec 05, 2005 4:54 pm
Location: Twitter: @dtabase

Postby MartinU » Mon Feb 14, 2011 1:23 pm

Thanks, many times it is the little things that make a big difference. You all do a great job of being involved with the "users" and I believe that is why your products are so successful.
MartinU
 
Posts: 13
Joined: Wed Feb 09, 2011 4:43 pm

Postby phil.monks » Fri Feb 18, 2011 4:47 pm

Hi,

We've been using SQL source control for a few months now and have recently noticed this issue.

Not syncing the column order is a big issue.

We've just had an issue where a developer had an INSERT that just listed the data to be inserted. This worked fine when they tested it and then failed when the stored procedure was promoted live as the developer didn't have the correct column order.

Whilst I understand that this is bad practice (and we have changed the SP), it does happen and it is valid.

This issue undermines the source control if the tables are not a mirror image.

Have you any indication as to when this feature may be implemented?

Thanks
phil.monks
 
Posts: 1
Joined: Fri Feb 18, 2011 4:37 pm

Postby David Atkinson » Fri Feb 18, 2011 5:04 pm

It's on our backlog and I would hope that we could squeeze this in before mid-year, although we can't make any hard commitments as we've also got static data to polish off, and object filtering to work on.

We'll do our best!

In the meantime please make sure that your insert statements reference the column names explicitly.

Kind regards,

David
David Atkinson
 
Posts: 1124
Joined: Mon Dec 05, 2005 4:54 pm
Location: Twitter: @dtabase


Return to SQL Source Control 1

Who is online

Users browsing this forum: No registered users and 0 guests