New DAL/BLL class for each table

Question

0.00/5 (No votes)

See more:

Should I make a new DAL/BLL class for each table that I want to access in the DB? Or should I just make a generic DAL/BLL class that can handle everything?

When I make new ones for each table, the code gets a bit repetitive, but it seems better than making generic classes.

Posted 6-Apr-14 0:19am

RexGrammer

Add a Solution

1 solution

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)

Abhinav S · Accepted Answer · 2014-04-06T00:34:00

Solution 1

I would recommend grouping items from a functional perspective. For eg. all authentication related items together, all database loading related items together and so on.

Posted 6-Apr-14 0:34am

Abhinav S