Be aware, though, that the objects will not have their instance
data returned to their state before the transaction started.
You’ll have to deal with that yourself (just as in the case of
Validations). Also have in mind that exceptions thrown within a
transaction block will be propagated (after triggering the
ROLLBACK), so you should be ready to catch those in your
application code.
One might want to consider using Transaction::Simple if you need
application-level rollback, not just database-level rollback. I have
not yet had time to implement a block form, but it is planned.
-austin
···
–
austin ziegler * austin.ziegler@evault.com
Austin Ziegler wrote:
Be aware, though, that the objects will not have their instance
data returned to their state before the transaction started.
You’ll have to deal with that yourself (just as in the case of
Validations). Also have in mind that exceptions thrown within a
transaction block will be propagated (after triggering the
ROLLBACK), so you should be ready to catch those in your
application code.
One might want to consider using Transaction::Simple if you need
application-level rollback, not just database-level rollback. I have
not yet had time to implement a block form, but it is planned.
Why not even add Transaction::Simple to Active Record?