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.