Comments
Sort by recent activity
Well, I can't see to catch a break! I decided to delete the migration script in source control (and commited its removal successfully), and now when I go to use SQL Compare (after closing it and reopening it) it STILL says "Error retrieving migration scripts". It's really got a bee in its bonnet about them now. / comments
Well, I can't see to catch a break! I decided to delete the migration script in source control (and commited its removal successfully), and now when I go to use SQL Compare (after closing it and re...
I decided to acknowledge the warning and proceed with the commit anyway (I'm linked to VisualSVN Server). This seemed to be successful, so I fired up SQL Compare and it's complaining as follows:
1 of 1 warning: Error retrieving migration scripts
The migration script was saved successfully to the repo because I did an SVN Update with TortoiseSVN on my computer and it brought down the new folder created especially for these scripts.
Now I am well and truly at a loss. I'll probably run my script customisations manually and just remove the allow nulls on the field afterwards, I guess. I'd still like to know why things are failing miserably. I don't think I'm asking too much of it :-) THanks. / comments
I decided to acknowledge the warning and proceed with the commit anyway (I'm linked to VisualSVN Server). This seemed to be successful, so I fired up SQL Compare and it's complaining as follows:
1 ...
By the way, it would nice if the following article explained more about the error, rather than just telling you how to ignore migration scripts altogether: http://documentation.red-gate.com/displ ... n+warnings
I do actually want to use a migration script, but it won't let me and won't tell me why. :-( / comments
By the way, it would nice if the following article explained more about the error, rather than just telling you how to ignore migration scripts altogether:http://documentation.red-gate.com/displ .....
If I click on the Migration Scripts tab it shows my one and only migration script and when I click edit, up it comes, and all my customisations are there. I've also closed/reopened SQL Compare several times. / comments
If I click on the Migration Scripts tab it shows my one and only migration script and when I click edit, up it comes, and all my customisations are there. I've also closed/reopened SQL Compare seve...
It seems that somebody already has, so I'll vote it up: https://sqltest.uservoice.com/forums/140716-sql-test-forum/suggestions/5888055-add-ability-to-edit-template-text
Thanks. / comments
It seems that somebody already has, so I'll vote it up:https://sqltest.uservoice.com/forums/140716-sql-test-forum/suggestions/5888055-add-ability-to-edit-template-text
Thanks.
Found it, the little black message-balloon button on the SQL Test pane. I think I preferred v 1.0 when there were labels beside buttons. / comments
Found it, the little black message-balloon button on the SQL Test pane. I think I preferred v 1.0 when there were labels beside buttons.
It seems that the filters that I added a few days ago have decided to take effect:
Schema:
Exclude if ( schema name beings with 'tSQLt' ) OR (object name begins with 'SQLCop' )
Stored Procedure:
Exclude if ( schema name beings with 'tSQLt' )
After removing them, they're appearing as things to commit in their own right, not as dependencies. But my filter didn't seem to prevent them being offered as dependencies until today, where I couldn't get it to nag me about dependencies if my life depended on it. Very strange. / comments
It seems that the filters that I added a few days ago have decided to take effect:
Schema:
Exclude if ( schema name beings with 'tSQLt' ) OR (object name begins with 'SQLCop' )
Stored Procedure:
Ex...
I came at it from the point of view that tSQLt is effectively a third-party library that I should always be getting from the supplier, and not committing to source control. I regarded it as a bit like committing some third-party DLLs, but perhaps it's not the right analogy.
I'll just commit them, then. Thanks. / comments
I came at it from the point of view that tSQLt is effectively a third-party library that I should always be getting from the supplier, and not committing to source control. I regarded it as a bit l...
Well, that's strange. Now that I've come to terms with committing tSQLt dependencies, it didn't offer to do so today, and I've got IgnoreTSQLT set to false, as well. I'll keep an eye on it
Thanks David. I am currently the only developer, but that might change one day, I guess. / comments
Well, that's strange. Now that I've come to terms with committing tSQLt dependencies, it didn't offer to do so today, and I've got IgnoreTSQLT set to false, as well. I'll keep an eye on it
Thanks D...
Thanks for reply, I didn't know about those settings (they're well hidden!).
Unfortunately setting IgnoreTSQLT to True excludes my test cases, and not just the tSQLt objects that my test cases depend on. It seems silly to be committing those to source control.
So I guess I should just commit all the tSQLt dependencies and move on? It would be nice if you had an IgnoreTSQLTDependencies option. / comments
Thanks for reply, I didn't know about those settings (they're well hidden!).
Unfortunately setting IgnoreTSQLT to True excludes my test cases, and not just the tSQLt objects that my test cases depe...