I posted some info/opinions yesterday on the CLR list. Should be in the archives. Topic was "Given DataView what is current row?" This was continued (steered over from) the old DOTNET list.
BTW, Microsoft is working on a generic O-R mapping layer/library called ObjectSpaces. There is a very old tech preview, but it is being entirely rewritten as we speak. There is no ETA yet. Cheers, Bob Beauchemin [EMAIL PROTECTED] -----Original Message----- From: Thomas [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 11, 2002 9:10 AM To: [EMAIL PROTECTED] Subject: [ADVANCED-DOTNET] Data Access API A number of people I have run into, and to some extend even I myself, have been confused about the use of ADO.NET datasets versus the concept of building your own Domain Object Model and using datareaders and commands to manage the db access portion of a system. I am wondering what experience the members of this list have had with ADO.NET. Have you found the productivity of a dataset outweighs the control of building your own Domain Model? What about the argument that the functionality that comes with datasets comes at a cost and frequently you don't need all that extra "stuff". Finally, is there any sort of information that determines the "cost" of a datasets functionality. By that I'm interested in an argument like " Yes certainly the dataset has extra functionality but it only adds XXX percent to the overhead of a given class or object." Maybe this isn't even a consideration at all? Anyways, the more feedback you could give the better. Or if this has been discussed on the list, could you refer me to the posts? Thanks Thomas You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
