Data Access Layer Question

C

Cirene

I am creating a DAL for my web application. Generally, should the code in
the DAL be kept generic so that it can be used in future projects, such as
ExecuteStoredProcedure, or ExecuteSQL?

Or is it better to put in the DAL any code that is "data related", such as
GetCustomer, DeleteProduct, ComparePrices, etc...

What is your opinion?
 
C

Cirene

Can you share it with me? :)

Mark Rae said:
That's good.


Yes, IMO.


No, IMO.

My DAL can be dropped unmodified into any new project, whether WebForms or
WinForms, and currently supports several RDBMS...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Testing your data access layer in another project part of samesolution 7
CODING PRACTICE. Business and Data Access Layers 6
Question on two 'flavors' of data access layers 3
Business Logic/Layer Question - Concept 2
validation sample code in Business logic layer and Data Access Lay 2
Web.config and app.config issues 4
DAL or BLL? How to implement objects 22
creating DAL, how???? 13

Top