Settings and activity
2 results found
-
4 votes
An error occurred while saving the comment An error occurred while saving the comment 
Anonymous
commented
Yes this has caused us some trouble as we have some developers working on another copy of the database (i.e. locally) while doing tSQLt unit testing. If they change the options to show tsqlt objects then the other users on the shared database have to view the tsqlt options which are not on the shared database and so it wants them to drop them. In past verisons we were able to sync the options from source control if we wanted or leave them specific to the task on a local database. It would be most appreciated if we were not forced to check in or get the latest database comparison options when changes exist. thanks.
Anonymous
supported this idea
·
-
17 votes
An error occurred while saving the comment Anonymous
commented
I have recently had the same problem and it is holding up the addition of one of our projects due to this error in our deployment process. Is there an update on this fix?
Anonymous
supported this idea
·
If groups are doing unit tests with tSQLt I almost think it would be necessary to have the option to keep database comparison options local and not required to update to or from. Maybe the option to keep the ignore tsqlt to local...