I am not sure if this is bug or intended behavior, just a difference observed between sqlcmd-go and sqlcmd (ODBC)

Tested on Ubuntu Linux machine with sqlcmd-go v1.8.2

Replication of this issue:

$ cat query.sql
SET NOCOUNT ON;
SELECT name FROM sys.databases;

// Outputs nothing
$ cat query.sql | sqlcmd-go

$ cat query.sql | sqlcmd-odbc
master
tempdb
model
msdb
...

I am not sure if this difference in behavior is intended. If I add go to the query, it works as usual for both