Benjamin Russell 11ca99f419 Handling NOCOUNT being set (#96) ...

After much thinking, this change brings the message behavior into line with SSMS, including if the NOCOUNT is set. This is a somewhat non-obvious solution, but the StatementCompleted event handler will only be fired if there is a record count to return. We'll add the message for number of records if the StatementCompleted event is fired, otherwise we won't add any messages while processing the resultsets of the batch. If any messages are returned from the server, we'll capture those. Then, if at the end of the batch, we haven't collected any messages from StatementCompleted events or server messages, then we'll add the "completed successfully" message.
This matches behavior of SSMS that will only emit a "completed successfully" message if there were no other messages for the batch.

* Solution to issue, some unit tests needed to be tweaked

* Comments for the event handler

2016-10-19 11:10:13 -07:00

..

CodeCoverage

Jenkins code coverage integration (#47)

2016-09-12 22:05:45 -07:00

Microsoft.SqlTools.ServiceLayer.Test

Handling NOCOUNT being set (#96)

2016-10-19 11:10:13 -07:00