Closed ellbosch closed 4 years ago
I'm fairly certain recent failures are due to PR validation build pipelines using the master DB, which tests in this branch don't support. Best we wait until #441 is approved.
Can you clarify what you mean by master db? master db should be read only, and tests should use their own database.
Can you clarify what you mean by master db? master db should be read only, and tests should use their own database.
Correct—with our stabilize DB PR, tests now generate a test DB if performing operations off of a database. Some tests were still performing commands off of the permanent DB we created, but that will all change once we merge #441.
In anticipation of this change, I set up or PR validation pipelines to no longer use the permanent DB, so we could properly test #441. This impacts other PRs (like this one) so it's best we wait to merge until #441 is complete.
Fixes #444.
The
--row-limit
arg was breaking mssql-cli because our code attempted to use a number operator on a string. The fix requires casting the parsed option as an integer.Notes:
row_limit
is validated in theMssqlCli
constructor, which uses a new_set_row_limit
method to validate a positive integer._set_row_limit
callssys.exit(1)
if an invalid value is provided.AttributeException
in the__del__
method because shutdown is called on an uninstantiatedsqltoolsclient
.