4 ms·
There should only be one using/try catch block on the highest level. All of the methods being called within that using block should just throw errors. You coul
by scarface74 7y ago
There should only be one using/try catch block on the highest level. All of the methods being called within that using block should just throw errors.
You could put the logic in attributes but I don’t consider a transaction a cross cutting concern. It would create a spooky action at a distance situation.
- logicalmind 7y agoIt's obviously highly dependent on the domain in which you work, but I would consider what you're saying to be a "business transaction" more than a "database transaction". If there is a 1:1 between the two then your way works. I tend to have situations where one business transaction is multiple database transactions. And the business transaction can succeed even if some of the underlying database transactions were to fail.