Where there is need for transaction(in the conventional sense of multiple SQL updates), I would. However, wrapping everything in a transaction is not something I want, many times it is not needed, just row level consistency is enough.
As for the set method, I know it is there. But we are talking about why people concern these individual field updates, not how to get around it. For the system I have worked with, these multiple updates(not multi-row as that can be atomic if it is within one SQL), they are done on the server with stored procedures. Kevin Dangoor wrote: > On 11/2/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > More than that. Transaction is one of the big topic on RDBMS. This per > > attribute update breaks row level consistency. > > Not if you're using transactions. Besides, it's easy to update > multiple columns at the same time if that's what you need to do... > just call instance.set(attr1='foo', attr2='bar') > > It's not uncommon to need to update multiple rows (and in different > tables, no less) at the same time, so using transactions is key to > data consistency. > > Kevin
