当您只是推迟到底层的sqlDataReader时,在包装器中实现IDataReader实际上并不难.它只是耗费一点时间而不是那么糟糕.

但我很好奇,你想要的资源是否已经解决了连接问题？如果是这样,CommandBehavior枚举的CloseConnection成员将确保在关闭数据读取器时关闭连接.

var reader = command.ExecuteReader(CommandBehavior.CloseConnection);
...
reader.Close(); // also closes connection

请注意,sqlDataReader上的Close / Dispose是相同的.

最后,这是最后一个在过去对我很好的建议.请注意,在下面的松散示例中,即使您在每个记录处“回放”给调用者,您也可以从头到尾拥有sqlDataReader.

private static IEnumerable<IDataRecord> GetResults(this sqlCommand command) {
    using (var myTicket = new MyTicket())
    using (var reader = command.ExecuteReader()) {
        while (reader.Read()) {
            yield return reader;
        }
    }
    // the two resources in the using blocks above will be
    // disposed when the foreach loop below exits
}

...

foreach (var record in myCommand.GetResults()) {

    Console.WriteLine(record.GetString(0));

}

// when the foreach loop above completes,the compiler-generated
// iterator is disposed,allowing the using blocks inside the
// above method to clean up the reader/myTicket objects