ID: 31315 User updated by: cryogen at mac dot com Reported By: cryogen at mac dot com Status: Wont fix Bug Type: Feature/Change Request Operating System: OSX Server 10.3.7 PHP Version: 5.0.2 New Comment:
Based on your reponse, I am not sure then why there are methods in mysqli supporting COMMIT and ROLLBACK when those can just as easily be sent to MySQL as SQl commands? Is there something special in how these work compared to their SQl language equivalents? Just trying to understand the PHP dev team's rationale for implementing some SQL commands and not other in the mysqli class. Thanks for the swift response. Previous Comments: ------------------------------------------------------------------------ [2004-12-27 23:37:27] [EMAIL PROTECTED] You can simply execute those queries yourself with mysqli::query(). We will not add methods for functionality that is already possible, and doesn't have a matching C API function. ------------------------------------------------------------------------ [2004-12-27 22:55:23] cryogen at mac dot com Description: ------------ I would like to suggest the addition of a START TRANSACTION or BEGIN method that would work along with the COMMIT and ROLLBACK methods already implemented in the mysqli class. It seems that the only examples using transactions always use $mysqli->autocommit(FALSE) in order to toggle autocommic on and off. It is not clear if this method turns autocommit on or off for the entire session, script, or just for the current transaction? Many of us prefer to leave autocommit on, and use the SQL commands"START TRANSACTION" or "BEGIN" which temporarily turn autocommit off for the current transaction. This seems a much cleaner way of performing transactions rather than turning off autocommit and then turning it back on for every transaction. Thanks for your consideration. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=31315&edit=1