Daniel Theophanes

Thanks. This can be part of a unit test, easier for me to see the problem. I'll look into it.

Thanks for the ping. This fell of my radar. Assigning to myself now.

We can fix this in go1.9. We can define top level types (mssql.Binary, mssql.Text, ...) and implement https://godoc.org/database/sql/driver#NamedValueChecker The NamedValueChecker. They pass the parameter into the driver like `db.Exec("SQL", mssql.Binary(nil))`...

Right now, not that I'm aware of. However, this is something I would personally like to enable in the future.

Oh, the driver already receives these messages. It is more of a question of `database/sql` API and how to expose them then anything.

Please see the proposal on issue https://github.com/golang/go/issues/19055 and the proposed CL https://golang.org/cl/39355 . This would allow dequeuing messages / print commands. Please comment as the the suitability of this API.

``` retmsg := &sqlexp.ReturnMessage{} rows, err := db.QueryContext(ctx, "PRINT 'hi'; select * from Account; PRINT hello';", retmsg) if err != nil { return err } defer rows.Close() switch msg :=...

@shueybubbles That would be great. It would need to be at the command level ideally anyway. If you wanted to stream messages, prior to receiving a result, you may be...

Yeah. Extract from the code the part that looks to see if the SQL text is a stored parameter or not. AS for the other one, no, not really. You...

Both are similar errors. Does this work if you run `go test -cpu 4` ? That would be unexpected, but interesting to know.