ADO.Net with Transcations

Question

0.00/5 (No votes)

See more:

Hi,

I'm writing a generic DAL layer for my development team because we dont want to give access of connection to the developers. I'm stuck in terms of providing option to handle Transaction oriented queries. Could some one throw light?

So, lets say I've 3 queries which have to be executed under one transaction. Since developer dont have access to Connection they can not create transactions.

Shall I take array of queries and parameters from client and execute within the Transaction Block? Is it a right approach.

Note:- I'm not using ORM hence I can not use Command Patterns also.

Thanks

Posted 9-Dec-10 18:53pm

satsumatable

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)

meaningoflights · Answer 1 · 2010-12-09T19:05:00

Why dont you want to give the developers access to the Connection object?

Sorry I dont think combining queries and executing them in a Transaction Block is the best approach. IMHO I think you should at least dev's access to some methods in the System.Transaction namespace.

See this article Introducing System.Transactions in the .NET Framework 2.0 and have a brainstorming session about giving your DAL some TransactionScope class lovin.