Avoid the possibility of exceptions in the constructor

[mortenbrudvik]

I think it would be better to create and open the connection at the first access to a repository. This is to avoid that you get an exception when you use Dependency Injection at the object creation, but also exceptions in constructor should generally be avoided.

I have done a similar implementation to your UnitOfWork. See link below
https://github.com/mortenbrudvik/SQLiteDapperConsole/blob/main/Infrastructure/UnitOfWork.cs

[timschreiber]

Because a transaction may involve operations in more than one repository (ie. deleting an order also needs to delete order items) creating the connection per repository will not work.

…

On Sat, Nov 14, 2020, 3:28 AM Morten Brudvik ***@***.***> wrote: I think it would be better to create and open the connection at the first access to a repository. This is to avoid that you get an exception when you use Dependency Injection at the object creation, but also exceptions in constructor should generally be avoided. I have done a similar implementation to your UnitOfWork. See link below https://github.com/mortenbrudvik/SQLiteDapperConsole/blob/main/Infrastructure/UnitOfWork.cs — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#11>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMMRPYYI6ZGI4AFXF2JJMTSPY5R5ANCNFSM4TVNJ5SA> .