Hello, I read quite a lot recently about Apache::DBI, transactions and the problems that might occur but I must say that I am more confused than before as to what this all means for my RDBO project.
It is a web app with lots of database activity (read and write). So performance and data integrity is an issue and my idea is to use Apache::DBI with autocommit => 0. As I understand it, this should speed things up, because the $dbh is shared and at the same time makes sure to do a rollback if it dies before a commit that would be placed near the end of the request. Is this understandig correct? If yes, my question is, how all the RDBO internals work with such a setup. If I remember correctly RDBO wraps complex saves or deletes within a transaction. Would this lead to something like nested transactions? Is this possible at all, with sqlite (I am using now) and postgres (I would like to use after some more learning)? And if it works in principle do I have to stuff the $dbh manually into every RDBO object or does it "just work" because Apache::DBI takes care that RDBO gets the right (perhaps reused) handle even if RDBO always requests a fresh one? Thanks for any help Michael ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
