Dynamic Data Access Layer in an n-tier application

Question

0.00/5 (No votes)

See more:

Good day fellow coders, I recently started to build n-tier applications (Presentation Layer, Business Layer and Data Access Layer) in C# and all is well. Until I came to data access layer, at the moment my DAL is static in the sense that for each table in my database I have a data access layer with the different select, update, delete and insert statements for that table for example I have a client data access layer and an order data access layer. Now the question I have is how to make a data access layer dynamic in other words only to use one dynamic data access layer which contains dynamic methods all the business layers can use to select,insert,update or delete data. Put simply I wish to use only one DAL instead of multiple for each table in the database. The purpose is for re-use ability. Please try to help. I would appreciate it!

Posted 16-Aug-11 8:21am

TheeStudent

Add a Solution

2 solutions

Solution 2

"Hence"?

Your second statement does not follow from the first.
It is NOT easier to understand a generic layer.

Other than that I mentioned "nHibernate" which an open source generic solution.

Posted 17-Aug-11 9:59am

jschell

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

jschell · Accepted Answer · 2011-08-16T08:45:00

Normal answer is that that isn't a good idea.

If you have a rather simple application then you can get by with nothing more than CRUD procs.

And with a simple application then it is much easier to debug, understand and maintain. So there isn't any point to attempt to drive to a generic layer.

In a more complex application there are more complex operations. Thus procs besides CRUD will be needed. The increased complexity is across the board and that extends to maintenance. A generic layer is thus a better solution as it is is more likely, at least to some degree, to reduce overall maintenance costs (trading complexity in one area for complexity in another.)

Now if you want to use another approach to learn how to do it and it seems likely that such an approach would benefit the company (or perhaps that is not a factor) then you might investigate alternatives.

If and only if that is the case then you might want to look at nHibernate.