Closed ellbosch closed 5 years ago
Considering possible test cases for -Q:
execute_query
outputexecute_query
outputAny others @pensivebrian? #Closed
Latest changes introduced a fix for a bug that caused crashes on exiting VIM mode and more tests. As a disclaimer—I've noticed that calling mssql-cli -Q ""
with empty strings will launch the default interactive mode. We should have further discussions about expected functionality for empty quotes. #Closed
things like this don't make sense in non-interactive mode. #Closed
Refers to: mssqlcli/mssql_cli.py:184 in 3700608. [](commit_id = 370060894b4248e957d3045062a47c04d4a98eb4, deletion_comment = False)
Skip in non-interactive mode?
Refers to: mssqlcli/mssql_cli.py:188 in fba47c5. [](commit_id = fba47c52b361544dd32efed4edf292d40b405912, deletion_comment = False)
Some minor comments. The only product issue, it in the MssqlCli constructor, we shouldn't be spinning up the completion refreshers or anything that doesn't make sense in non-interactive mode.
Ok, will give this a shot.
@pensivebrian very curious about your thoughts with this commit, which will only set various properties in MssqlCli
class if interactive mode is set. Tests have passed with these changes but I want to be sure that there aren't any unintended consequences.
Looks good. I’d still take the tool for a good test spin manually, querying and changing database to make sure it works.
My latest changes fix all known python 2 issues. So far all tests have passed, I've also successfully created builds remotely on Azure. I'm running one more just to be sure.
This PR would close #242. Unit tests have not been covered yet. Thoughts on the implementation @pensivebrian?