Can anyone confirm whether this is correct:
a) If you are an update to a model that has relations, rails automatically handles updating the relationship table as required and wraps everything itself in a transaction
Yes.
b) If you are doing multiple updates within the same model => wrap a
transaction around it yourself
Yes.
c) If you are doing multiple updates across various models => wrap a
transaction around it yourself (??is this correct??) and it will be handled
Yes.
d) If you want to have your model objects (as well as database) accurate after a failure/rollback then list the object explicitly as parameters to the transaction( ) method. "There’s a downside to having the
transaction code recover object state automatically—you can’t get to any error information added during validation" (from AWDR) ==> QUESTION: Is this last point an issue? do people usually not worry about trying to get their model recovered
correctly? i.e. as it would be re-generated with the next web request anyway?
You usually want the record in its dirty state so you can present the errors to the user. Object transactions are marginally useful and will be spun off into a plugin after Rails 1.2.
jeremy
