Re: Committing rolling back many objects at once?

[prev] [thread] [next] [Date index for 2005/01/25]

Perrin Harkins wrote:
> Even so, it's important for users to understand that this is all tied to
> the database connection, not to any specific set of objects.  Class::DBI
> just calls commit on your database connection, and adds nothing on top of
> that to tie transactions to objects.

Yep.  The flipside of this is that after you commit a transaction, you
don't know that the versions of objects you hold in memory correspond to
the versions in the database.

So, clearing cached forms of an object after a transaction cycle is a
good idea to avoid medium term "dirty read" problems.
        -- 
        Sam Vilain, sam /\T vilain |><>T net, PGP key ID: 0x05B52F13
(include my PGP key ID in personal replies to avoid spam filtering)