Can we declare data access layer class as non static class. If so will it leads to transactions problem?

Question

1.00/5 (1 vote)

See more:

Hi All,

I'm very much confused for the reason of declaring DAL(Data Access Layer) Class as static. If i declare DAL(Data Access Layer) class as non static will it leads to transaction problem.

For Example: My application DAL(Data Access Layer) classes are in non static. Whenever users access that it will create new instance of that class. When two users accessing same field in table in same time. Will it leads to transaction when any user is in slow net connection.

Posted 21-Mar-12 20:04pm

HarisJayadev

Add a Solution

Comments

Dean Oliver 22-Mar-12 2:13am

What technology are you using? EF? Linq To Sql? old ADO.NET? And where did you read it has to be static? and whats in this class? Please provide sample code. thanks

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)

OriginalGriff · Accepted Answer · 2012-03-21T22:16:00

It's not the users that are the problem - it's the potential for having two instances within the same application.

Even if you declare it as static, you can have two users accessing the same database from different PCs - which could cause transaction problems and has to be kept in mind when designing any system. Static or non-static will not affect that.

Static just prevents there being two incompatible versions of the data layer as seen by the program. It's not necessary, and can prevent some patterns (such as the Factory pattern) being used. Static, Singleton, or instanced - it is a matter of personal preference to a large degree.