Ambient transactions and database connections

For an application using System.Transcations, what’s the best way to ensure that
Linq2db uses the same database connection for all commands in the same transaction scope?

In the code like the following, I’d like to ensure that dc1.Connection and dc2.Connection
will be the same IDbConnection instance to avoid escalating to the distributed transaction:

using (var scope = new TransactionScope()) 
{
     Service1.DoStuff();
     Service2.DoMoreStuff();
     scope.Complete();
}

class Service1
{
     public void DoStuff()
     {
	       using (var dc1 = new DataConnection())
	       {
	          dc1.SetCommand(...).Execute();
	       }
     }
}

class Service2
{
     public void DoMoreStuff()
     {
	       using (var dc2 = new DataConnection())
	       {
	          dc2.SetCommand(...).Execute();
	       }
     }
}

As a workaround, I’m currently using a custom data provider that returns the same
connection for each ambient transaction instead of creating a new one every time.

The code worked fine in BLToolkit and works just as well in Linq2db but I’m wondering
if there is a better way supported by Linq2db?

[jods4]

@yallie are you sure that works in raw ADO.NET?

I don’t know the Postgre provider, but in other providers I wouldn’t expect that to work.

You create two different connection to your DB, at best with a distributed transaction, I wouldn’t expect them to share temporary tables.

[yallie]

Problem is that there is no API to get connection, associated with Transaction.Current, so you need to store this information somewhere.

Yes, exactly!

You can achieve it with something like that:

That’s right, I’m currently using a similar piece of code 😃