outmatic / dapper.unitofwork Goto Github PK

Hello,

Do you have a simple example, how to implements?

Tks,

Is it possible to create a IDbConnection with npgsql connection so that it can be used with postgres db?

Does Dapper.UnitOfWork support NETCORE?

Hi there, how does rollback occours in your code ?
Lets say i have a table with the following fields:

-Id (Int, Key, Auto Increment)
-Name(Nvarchar, Constraint, Not Null)
-Age(Int, Null)

When i try to insert two people in row like.

using(var uow = repositoryFactory.Create(true)){
    uow.Execute(new AddPersonCommand(PersonInstanceOne));
    uow.Execute(new AddPersonCommand(PersonInstanceOne));
    uow.Commit();
}

The first query executes without any throuble as it should, but after the second query where i try to insert an existing constraint i get the exception but the commit accours for the first query.

My repository's execute method looks like this:

public void Execute(ICommand command){
        if (command.RequiresTransaction && _transaction==null)
            throw new Exception($"Error")

        try{
            command.Execute(_connection, _transaction)
        } Catch(SqlClient.SqlException ex
            Debug.WriteLine($"Error: {ex.Message}")
        }
}

Hi again, last week i've forgot to ask you if there were deadlocks or any other async/sync tests for your async methods within sync methods.

In your example, line 36, you're calling the method MainAsync within a sync method, but i also read that the console's Main method may be an exception to these cases where you can actually call an async method and get fine with it in most cases without causing the application to crash.

MainAsync(args).GetAwaiter().GetResult();

The fact that this code will run synchronously may be a problem in most of the cases, after some reading on "don't block asynchronous code". As it looks, it may be there just for demonstration purposes and no real application at all, but i couldn't avoid to look at the same call in Retry.cs, line 34.

HandleExceptionAsync(retryOptions, ex, retryCount).GetAwaiter().GetResult();

After some reading and research about this method, i've found some warnings like "they're meant to be used by the compiler" and "they may cause deadlock".

All these approaches seems more like a way to unwrap the exceptions being thrown if any. My big question is: Is it safe to use GetAwaiter().GetResult() in this context ?