Re: Return DataReader From Method; Good or Bad Practice?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Ravichandran J.V. (jvravichandran_at_yahoo.com)
Date: 03/23/04


Date: Tue, 23 Mar 2004 01:38:33 -0800

Functionally, a DAL should be returning a DataSet rather than a
DataReader because the layer's functionality is to provide data and to
have a connected access scenario may seem like bad practice. But then,
it is also according to preferences at times.

with regards,

J.V.Ravichandran
- http://www.geocities.com/
  jvravichandran
- http://www.411asp.net/func/search?
  qry=Ravichandran+J.V.&cob=aspnetpro
- http://www.southasianoutlook.com
- http://www.MSDNAA.Net
- http://www.csharphelp.com
- http://www.poetry.com/Publications/
  display.asp?ID=P3966388&BN=999&PN=2
- Or, just search on "J.V.Ravichandran"
  at http://www.Google.com

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!



Relevant Pages

  • Re: What Is The Best Way To Get A RecordSet ?
    ... Depending on the functionality you need, a datareader may be more costly ... It's certainly faster in a head to head comparison, ... datatables are the way to go for most of that. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: to use or not to use a dataset
    ... what is a strongly typed datareader? ... (While you even can take a part of the name of the textbox when you make ... I get as well the idea that you say using datatables makes things simpler, ... even less functionality from that) ...
    (microsoft.public.dotnet.framework.adonet)