Transactions not being passed to dapper

[rmedcalf]

I have a filter in my API that handles transactions automatically. It starts a transaction on any POST, DELETE, PUT, request. At the end of the request it commits it if no errors, otherwise rolls back.

So any of the extension methods that I use, whether it's a .Get(), .First(), or an .Insert() or .Update() it throws an error saying that a transaction is required.

[IssueHuntBot]

@BoostIO funded this issue with $10. Visit this issue on Issuehunt

[ahmad-moussawi]

I propose the following API

db.Transaction(() => {

   db.Update(...);
   db.Update(...); 

})

any exception thrown inside the callback function will rollback the transaction

db.Transaction(() => {

   db.Update(...);
   db.Update(...); 

  if(someError)
  {
   // throw exception to rollback
   throw new Exception("...");
  }

})

[julioleitao]

Does this issue still relevant for the project? It is interesting to have someone to work on it?

[ahmad-moussawi]

@rmedcalf @julioleitao all execution methods now starting from (2.2.0) accept the transaction as optional parameter.