You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been debugging an issue with MARs recently where despite MARs being set to false, the connections still seem to run with _pMarsPhysicalConObj. To try and get further information on this, I turned on verbose logging with a SQL listener and discovered your format string and output are mismatched.
Inside the method TraceString inside TdsParser.cs you have an extra "" for the log which throws things off and you see as the output I get
Thanks! If you do shift them up you get _fMARS is false but _pMarsPhysicalConObj is true. Any pointers on how this could happen? Trying to debug myself before raising another issue :)
Describe the bug
I've been debugging an issue with MARs recently where despite MARs being set to false, the connections still seem to run with _pMarsPhysicalConObj. To try and get further information on this, I turned on verbose logging with a SQL listener and discovered your format string and output are mismatched.
Inside the method TraceString inside TdsParser.cs you have an extra "" for the log which throws things off and you see as the output I get
As you can see, _fMars is coming out as 75 and isYukon as (null). I believe they are all shifted by one.
To reproduce
Not needed really - bug is clear I hope!
Expected behavior
Log should print correctly
Further technical details
Microsoft.Data.SqlClient version: 2.1.1
.NET core: 3.1
The text was updated successfully, but these errors were encountered: