Database transactions in Zend Framework: Are they isolated?

Presupposing you are using the InnoDB engine for tables that you will issue transactions on: If the requirement is that you first need to read the row and exclusively lock it, before you are going to update it, you should issue a SELECT ... FOR UPDATE query. Something like: $db->beginTransaction(); try { $select = $db->select() ->forUpdate() // from( array( 'a' => 'yourTable' ), array( 'your', 'column', 'names' ) ) ->where( 'someColumn =? ', $whatever ); $result = $this->_adapter->fetchRow( $select ); /* alter data in $result and update if necessary: */ $db->update( 'yourTable', $result, array( 'someColumn =?' => $whatever ) ); $db->commit(); } catch( Exception $e ) { $db->rollBack(); } Or simply issue 'raw SELECT ... FOR UPDATE and UPDATE SQL statements on $db of course.

Presupposing you are using the InnoDB engine for tables that you will issue transactions on: If the requirement is that you first need to read the row and exclusively lock it, before you are going to update it, you should issue a SELECT ... FOR UPDATE query. Something like: $db->beginTransaction(); try { $select = $db->select() ->forUpdate() // from( array( 'a' => 'yourTable' ), array( 'your', 'column', 'names' ) ) ->where( 'someColumn =? ', $whatever ); $result = $this->_adapter->fetchRow( $select ); /* alter data in $result and update if necessary: */ $db->update( 'yourTable', $result, array( 'someColumn =?' => $whatever ) ); $db->commit(); } catch( Exception $e ) { $db->rollBack(); } Or simply issue 'raw' SELECT ... FOR UPDATE and UPDATE SQL statements on $db of course.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.