On 3/16/07, Christopher H. Laco <[EMAIL PROTECTED]> wrote:
> My point is, there's no sane way to do a big jumble of code in one DB
> transaction without having to go code diving for a dbh to work against,
> ala 'local $dbh->{AutoCommit} and such.
So you're saying that one of your tools is trying to do automatic
commits for you. Which one?
> If I'm working in a Catalyst app, and I need $c->model('DBModuleOne')
> and $c->model('DBModuleTwo') to do some work, and both either commit or
> rollback, I have to do module diving to get at each models dbh and write
> mode transaction management code.
Those database objects shouldn't be handling transactions. They are
too low-level for that. Methods above them that you write should do
all of the transaction handling.
- Perrin
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Rose-db-object mailing list
Rose-db-object@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rose-db-object
