HasRows fails to detect rows

[wilfre]

Describe the bug

For queries that do have records, SqlDataReader.HasRows method returns false when the DB returns more than 1 InfoMessageToken, before sending a RowToken, HasRows assumes no records are left, and returns false even though it should have been true.

Using a db that returns two infomessages in the beginning is enough to reproduce the behavior.

string connectionString = "....";
var conn = new SqlConnection(connectionString);
conn.Open();

conn.InfoMessage += (sender, e) => Console.WriteLine(e.Message);

var cmd = conn.CreateCommand();
cmd.CommandText = "PRINT('1');SELECT * FROM t1";
using (var dr = cmd.ExecuteReader())
{
    Console.WriteLine($"HasRows: {dr.HasRows}"); // will return false if 2 infoMessages are sent by the DB.
    while (dr.Read())
    {
        Console.WriteLine(dr[0]);
    }

}

Expected behavior

HasRows shoud return true.

Additional context
When trying to identify the issue we encounter that this should probably be a while instead of an if statement.

[SubhankarPriyaranjan]

using (var dr = cmd.ExecuteReader())
{
do
{
if (dr.HasRows)
{
while (dr.Read())
{
Console.WriteLine(dr[0]);
}
}
} while (dr.NextResult());
}

[MichelZ]

Can you elaborate on this?
I have not been able to reproduce this.

Can you modify the following unit test so it fails for what you want to show?

[Fact]
public void Test1()
{
    int rows = 0;
    int infoMessages = 0;
    using (var conn = new SqlConnection("Data Source=tcp:localhost;Initial Catalog=Northwind;User ID=sa;Password=Just1Testing;Encrypt=False;Connect Timeout=300"))
    {
        conn.Open();

        conn.InfoMessage += (sender, e) => infoMessages++;

        var cmd = conn.CreateCommand();
        cmd.CommandText = "PRINT('1'); PRINT('2'); SELECT * FROM Customers";
        using (var dr = cmd.ExecuteReader())
        {
            Assert.True(dr.HasRows);
            while (dr.Read())
            {
                Assert.True(dr.HasRows);
                rows++;
            }

        }

        Assert.True(rows > 0);
        Assert.Equal(2, infoMessages);
    }
}

[wilfre]

Hi, sorry for the confusion; but the code I pasted there actually does not reproduce the bug, it would be reproduced if the database could return two INFO tokens, similar to: Statement IDs.