You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version of the script
Current dev-branch at GitHub
What is the current behavior?
The table dbo.SqlServerVersions is only dropped in current database
The table dbo.SqlServerVersions is dropped regardless of @printOnly
The drop statement is not included in the PRINT output
If the current behavior is a bug, please provide the steps to reproduce.
Just have a look at the code:
What is the expected behavior?
In the first case (only current database) I am not sure, because it may be risky to delete all tables dbo.SqlServerVersions in all databases.
In the second case (regardless of @printOnly) I would expect that @printOnly does not delete any objects, so does not drop the table.
In the third case (PRINT output) I would expect the DROP TABLE to be included in the PRINT. This is how I found the bug: I have missed the statement and so I had a look at the code.
If you want me to code that and open a pull request, just give me a hint.
The text was updated successfully, but these errors were encountered:
Version of the script
Current dev-branch at GitHub
What is the current behavior?
The table dbo.SqlServerVersions is only dropped in current database
The table dbo.SqlServerVersions is dropped regardless of @printOnly
The drop statement is not included in the PRINT output
If the current behavior is a bug, please provide the steps to reproduce.
Just have a look at the code:
SQL-Server-First-Responder-Kit/Uninstall.sql
Lines 76 to 77 in 0e76863
What is the expected behavior?
In the first case (only current database) I am not sure, because it may be risky to delete all tables dbo.SqlServerVersions in all databases.
In the second case (regardless of @printOnly) I would expect that @printOnly does not delete any objects, so does not drop the table.
In the third case (PRINT output) I would expect the DROP TABLE to be included in the PRINT. This is how I found the bug: I have missed the statement and so I had a look at the code.
If you want me to code that and open a pull request, just give me a hint.
The text was updated successfully, but these errors were encountered: