Using DbContext in nested scope

Hi.

I created class marked with [UnitOfWork(isTransactional: true)] attribute. Then i injected IRepository<Entity> into ctor.

In method i create something like this:

var xx = repTest.GetAll().Take(1).ToList();
using (var uov = uowManager.Begin(new UnitOfWorkOptions()
                {
                    Scope = System.Transactions.TransactionScopeOption.Suppress,
                    IsTransactional = false,
                }))
                {
                    var xx = repTest.GetAll().Take(1).ToList();
                    uov.Complete();
                }

If i look into SQL profiler first request is create inside transaction (SPID: x) and second outside of transaction (SPID: y). So everything work perfect and as expected.

If i replace repository with dbcontext then second query is executed inside of transaction (same SPID). Why is that ? I have injected IDbContextProvider<TestDbContext> into ctor and then get context from provider (calling .GetDbContext method).

Please explain why ABP works like that. Is this bug ?

Thanks for advance.

Edvin

[acjh]

From the MSDN article on The Repository Pattern:

Use the Repository pattern to achieve one or more of the following objectives:

• You want to maximize the amount of code that can be tested with automation and to isolate the data layer to support unit testing.
• You access the data source from many locations and want to apply centrally managed, consistent access rules and logic.
• You want to implement and centralize a caching strategy for the data source.
• You want to improve the code’s maintainability and readability by separating business logic from data or service access logic.
• You want to use business entities that are strongly typed so that you can identify problems at compile time instead of at run time.
• You want to associate a behavior with the related data. For example, you want to calculate fields or enforce complex relationships or business rules between the data elements within an entity.
• You want to apply a domain model to simplify complex business logic.

So yes, we generally avoid using DbContext directly.

The limitation is that IRepository only has methods that use a subset of DbContext methods. In other cases, using DbContext may be necessary. That’s where Custom Repositories come in.

[acjh]

You are using the context from the outer unit of work. Try this:

public void TestMethod()
{
    var ctxTest = dbContextProvider.GetDbContext(MultiTenancySides.Tenant);
    var data1 = ctxTest.DataForSend.Take(1).ToList();
    using (var uov = uowManager.Begin(new UnitOfWorkOptions()
    {
        Scope = System.Transactions.TransactionScopeOption.Suppress,
        IsTransactional = false,
    }))
    {
        var ctxTest2 = dbContextProvider.GetDbContext(MultiTenancySides.Tenant); // Add this
        var data2 = ctxTest2.DataForSend.Take(1).ToList(); // Modify this
        uov.Complete();
    }
}