For future reference ....
1. DataReaders have less overhead than DataSets and are more efficient.
2. DataReaders can be databound (i.e. to a DataGrid).
but
1. DataSets are disconnected. They are like disconnected models of the database.
2. DataSets can be made into Session objects or files, for persistence (which I need)
3. DataSets can provide access to more than one table and table relationships
4. DataSets can be bound to multiple controls and/or reiterated through multiple times whereas a DataReader is a once through.
5. You can jump to a particular record or go backwards through a DataSet.
Also, if you name your table then you don't have to worry about getting the right Table[i]!!
I'm working on a project to syndicate library content with RSS.... and learn .NET, C#, and AJAX
Thursday, July 12, 2007
DataSet vs. DataReader
Posted by Jody Condit Fagan (JCF) at 10:27 AM
Labels: datareader, dataset
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment