SqliteCommand.ExecuteReaderAsync with CommandBehavior.CloseConnection appears broken

[tdinucci]

Edit: This issue is present in v2.2.1 but not v2.0.0

When creating an SqliteDataReader using CommandBehavior.CloseConnection from an SqliteCommand which is disposed the reader and connection are closed prematurely.

Steps to reproduce

using (var cmd = GetDbCommand(statement))
{
     if (cmd.Connection.State != ConnectionState.Open)
         cmd.Connection.Open();

    cmd.CommandType = statement.Type;
    if (statement.Parameters != null)
    {
        // AddRange(...) seems to have a bug in SqliteCommand
        foreach (var parameter in statement.Parameters)
            cmd.Parameters.Add(parameter);
     }
    return await cmd.ExecuteReaderAsync(CommandBehavior.CloseConnection).ConfigureAwait(false);
}

Further technical details

Operating system: Ubuntu 18.04

From a very quick look it seems that the call shown below to this.DataReader.Dispose() on SqliteCommand is being called and the CommandBehavior is ignored.

private void DisposePreparedStatements(bool disposing = true)
{
    if (disposing && this.DataReader != null)
    {
        this.DataReader.Dispose();
        this.DataReader = (SqliteDataReader) null;
    }
    ...
}

[ajcvickers]

@bricelam to investigate for patch.

[bricelam]

Duplicate of aspnet/Microsoft.Data.Sqlite#484

BUT the architecture I have in mind for #14044 will remove the need to dispose SqliteCommand objects. It will also allow them to be disposed while their SqliteDataReader is open.

[bricelam]

The workaround for your specific case is to not dispose the command object. It will get disposed when the connection is closed.