Hi, [transactions] > thats a good question, since we have webtriggered actions, and if the > script finishes... how the transaction behaves? or how do i get back to > the 'started' transaction in the next script? > >> If yes, then we need to propagage the transaction to each method >> that operates on the transaction. After the last operation has >> finished, the transaction may be closed with a commit. >> > i think, we need, otherwise it could get difficult in my eyes
I am not sure, the DBI connection is handled by the OpenCA daemon and not by the CGI, so theoretically it is possible to keep the transaction open even across user commands. But depending on the transaction isolation level that was chosen this might influence the responsiveness of the whole application for other user, in the highest isolation levels the DB operations are fully serialized. I remember Michael saying that transactions are kept even across multiple calls from OpenCA. So our discussion may be moot. Michael? Martin ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ OpenCA-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/openca-devel
