DataReaders vs DataSets

[sevenhalo]

DataReaders. .Net is very very OOP purist friendly. The dataset (unless it's typed) is a generic housing container for any kind of data. Naturally, that comes with overhead. With a DataReader, I can take the data, place it into my objects I created and be done with the reader. I'm not stuck maintaining a recordset anymore and quite frankly - that is one of the things I love about .Net the most.

[Hack]

I'm not stuck maintaining a recordset anymore

I'm not quite sure what you mean by maintain. Whenever I created a recordset, I used, then closed it and set it to nothing. Whats to maintain?

I'm doing the same thing with the reader (which, just based on two posts, I think I'll stick with). I create, use it, and close it. I see the way I'm using the reader to be nearly identical to the way I used recordsets.