Doc #65978 [Opn->Csd]: mysqli.commit examples flawed

Edit report at https://bugs.php.net/bug.php?id=65978&edit=1 ID: 65978 Updated by: kalle@php.net Reported by: kbcmdba at gmail dot com Summary: mysqli.commit examples flawed -Status: Open +Status: Closed Type: Documentation Problem Package: Documentation problem Operating System: Any PHP Version: 5.5Git-2013-10-28 (Git) -Assigned To: +Assigned To: kalle Block user comment: N Private report: N New Comment: This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. Previous Comments: ------------------------------------------------------------------------ [2013-11-16 23:26:33] kalle@php.net This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. ------------------------------------------------------------------------ [2013-10-28 00:55:52] kbcmdba at gmail dot com Description: ------------ The example shown in the mysqli.commit page is flawed. It suggests that users simply commit without checking to see if the commit succeeded or not. As a MySQL DBA, I see this with developers very commonly - they assume that issuing a commit will always succeed and conflicts never happen. You can help guard against that misconception. Please stop perpetuating the problem by showing developers that it's wise to verify commits actually did commit successfully. Even when autocommit is turned on, it's still wise to verify that the operation succeeded. Just because a user is using InnoDB doesn't guarantee that there won't be conflicts. --- From manual page: http://www.php.net/mysqli.commit --- Test script: --------------- Any script that creates a conflicting change in a separate transaction will cause this to fire off. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=65978&edit=1