From: ExsonQu <hex...@gm...> - 2016-07-07 12:53:55
|
*Dear all,* I've found the reason for the atomic transaction feature failure. It is caused by the "Lock Table" sql statement which causes a implicit commit. In order to fix this problem, we have to move the GetNextTransNo function outside of the transaction begin statements or remove the lock table sql statement. Is any idea for this? Thanks and best regards! Exson ExsonQu wrote* > Dear all, * > > I found a serious problem in WorkOrderReceive.php during > fixing a bug. > > The transaction roll back failed for following query > statement ( It's around at line 450~454). > > $SQL = "UPDATE locstock > SET quantity = locstock.quantity + " . $QuantityReceived . " > WHERE locstock.stockid = '" . $_POST['StockID'] . "' > AND loccode = '" . $_POST['IntoLocation'] . "'"; > > All of others queries have been rolled back, but only > this one failed. It leads to stock quantity updated so the inventory > quantity become a mess. > > Any comments are highly appreciated! > > Thanks in advance! > > Best regards! > > Exson -- View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Transaction-s-Rollback-failed-tp4658233p4658628.html Sent from the web-ERP-developers mailing list archive at Nabble.com. |