public static IEnumerable Enumerate(this IDataReader reader) {
  using (reader)
    while (reader.Read())
      yield return reader;
}

It seems logical that we really have two responsibilities here. One to enumerate a sequence of IDataRecord instances and another to coordinate with a mapping delegate and our friend the ExecuteReader() method.

-jimmy

[)amien

And another to do the map:

var customers = Mapper.Map<IDataReader, IEnumerable>(dataReader);

Could probably bake that into your extension method style quite nicely:

public static class DataHelpers {
    public static IEnumerable<Customer> As<T>(this DbCommand command) {
        using (var reader = command.ExecuteReader(CommandBehavior.CloseConnection)) {
            return Mapper.Map<IDataReader, IEnumerable>(dataReader);
        }
    }
}

Or heck, skip the CreateMap step if you don’t need anything fancy (i.e. your domain object properties are 1-1 with column names) and change that line in the extension to this:

return Mapper.DynamicMap<IDataReader, IEnumerable>(dataReader);

var customer = new CodingHorror("SELECT * FROM Customer WHERE ID=@1",1).ExecuteSingle();

But if you think FluentADO is “too big” then you might think SubSonic is as well :).

FluentADO sounds like a nice idea but it is still too large for this little prototype and these methods are working a treat.

[)amien

It really helps with discoverability – no more what class is that static method on that takes a string and does x with it? Well, it appears alongside x and it doesn’t break encapsulation as it still only has access to the public interface.

[)amien

Also, be sure to check out iBatis (think of it as the data-mapping functionality of NHibernate without all the session and reference stuff), this is good for building an ORM with legacy databases.

Also check out BLToolKit, which makes ORM dead simple for basic queries.