txn attribute is no longer meaningful after Spring change
Kelven
On 9/4/13 9:46 AM, "Darren Shepherd" wrote:
>I see @DB(txn=false) a lot in the code. The javadoc says "By marking
>txn=false the method is not surrounded with transaction code" but I
>can't find any code that backs up this claim.
I see @DB(txn=false) a lot in the code. The javadoc says "By marking
txn=false the method is not surrounded with transaction code" but I
can't find any code that backs up this claim. I only can find the below
code in com.cloud.utils.db.TransactionContextBuilder that seems to point
to the fact
Believe so. Here's a review removing that txn reference:
https://reviews.apache.org/r/12134/
It hasn't been applied yet. Still waiting for more eyes on it.
On Wed, Sep 04, 2013 at 09:46:37AM -0700, Darren Shepherd wrote:
> I see @DB(txn=false) a lot in the code. The javadoc says "By
> marking t