Issue
When calling DB to connect to an sqlserver database, a spawned command window stays open and vim hangs until the window is closed. (names below are redacted for security)
Notes
This behavior does not happen when using osql in place of sqlcmd. In that case, there is no spawned command window left hanging open, and dadbod works as expected.
Desired Outcome
I would like to be able to use sqlcmd rather than osql because sqlcmd has the -W option that will trim trailing whitespace from the query results. Without trimmed trailing whitespace, for the db's I am working with, the fields are returned absurdly long, making the output nearly unreadable.
What I've Tried
Skimming the dadbod code for clues about how input/output are handled. Unfortunately, my combined vimscript and windows command line skills are too weak given the time I have for debugging.
Swapping out sqlcmd for osql. The results of that are included in the write-up above.
Environment Vim8 on Windows7
Issue When calling
DB
to connect to an sqlserver database, a spawned command window stays open and vim hangs until the window is closed. (names below are redacted for security)Notes This behavior does not happen when using
osql
in place ofsqlcmd
. In that case, there is no spawned command window left hanging open, and dadbod works as expected.Desired Outcome I would like to be able to use
sqlcmd
rather thanosql
becausesqlcmd
has the-W
option that will trim trailing whitespace from the query results. Without trimmed trailing whitespace, for the db's I am working with, the fields are returned absurdly long, making the output nearly unreadable.What I've Tried
sqlcmd
forosql
. The results of that are included in the write-up above.