Comments
Sort by recent activity
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 / comments
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 INSE...