| Showing all 25 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 27536 | 2007-03-29 20:09 | 2007-04-11 9:21 | MySQL Server | Can't repeat (6218 days) | S1 | 5.1.16 | Linux (linux) | Any | INSERT INTO ... VALUES (),(),...,() + autocommit enabled not Atomic!! |
| 26266 | 2007-02-11 10:14 | 2008-01-03 7:18 | MySQL Server | Can't repeat (5951 days) | S3 | 5.2,5.1 | Linux (Linux, windows) | Any | autocommit not visible in SHOW VARIABLES output |
| 34541 | 2008-02-14 11:09 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5556 days) | S2 | 5.1 | Any | Any | mysqlbinlog prints 'set;' in stm mode after changing autocommit mode |
| 34839 | 2008-02-26 13:12 | 2008-02-26 13:45 | MySQL Server: Information schema | Not a Bug (5897 days) | S3 | 5.1.22 | Any | Any | Values in variable and information_schema do not match for autocommit |
| 31598 | 2007-10-15 9:41 | 2007-11-05 20:17 | MySQL Server: Documentation | Closed (6010 days) | S3 | 4.1.22, any? | Any | Any | set autocommit=1. Does it always commits transaction implicitely? |
| 37568 | 2008-06-22 13:49 | 2008-06-22 23:28 | MySQL Server: Documentation | Closed (5780 days) | S3 | 5.0,5.1,6.0 bzr | Any | Any | autocommit wronly documented to work in option files and command line |
| 43073 | 2009-02-21 7:07 | 2011-02-25 23:03 | MySQL Server: Locking | Not a Bug (4802 days) | S2 | 5.0.32-Debian_7etch1-log | Other | Any | START TRANSACTION and COMMIT do NOT change AUTOCOMMIT |
| 33258 | 2007-12-15 9:06 | 2010-05-26 17:59 | MySQL Server: Falcon storage engine | Unsupported (5077 days) | S3 | 6.0.5 | Any | Any | Misleading Error when DROP TABLE operation while a transaction is open |
| 47799 | 2009-10-02 16:54 | 2009-10-07 14:06 | MySQL Server: Stored Routines | Not a Bug (5308 days) | S3 | 5.1.34 | Linux (RH4U6) | Any | Could not modify sql_mode within stored procedure |
| 53211 | 2010-04-27 16:01 | 2010-04-28 14:48 | MySQL Server: InnoDB storage engine | Not a Bug (5105 days) | S2 | 5.1.42 | Other (Fedora 11) | Any | committed data is not visible to other sessions when autocommit is off |
| 60262 | 2011-02-26 1:01 | 2011-02-26 17:19 | MySQL Server: C API (client library) | Not a Bug (4801 days) | S2 | 5.5.9 | Windows (Windows7 on server and client) | Any | client side commit strangeness when autocommit disabled (with innodb) |
| 47436 | 2009-09-18 10:27 | 2011-11-02 9:21 | MySQL Server: InnoDB storage engine | Verified (4552 days) | S2 | 5.1.38 | Linux | Any | Transaction isolation level SERIALIZABLE becomes REPEATABLE-READ in autocommit |
| 63781 | 2011-12-17 13:44 | 2012-01-18 1:00 | MySQL Server: Replication | No Feedback (4476 days) | S2 | 5.5.17 | Any | Any | Changes done by replication slave not seen unless commit on slave is issued. |
| 61391 | 2011-06-02 20:48 | 2011-06-03 18:50 | MySQL Server: Locking | Not a Bug (4704 days) | S2 | 5.5.8 | Linux | Any | Metadata lock held on MyISAM table when AUTOCOMMIT turned off |
| 64923 | 2012-04-10 9:03 | 2012-04-12 20:16 | MySQL Server: InnoDB storage engine | Duplicate (4390 days) | S2 | Server version: 5.1.52 | Any | Any | inserted rows not visible to other sessions after commit (autocommit off) |
| 66884 | 2012-09-20 3:16 | 2017-01-09 18:04 | MySQL Server: Options | Verified (4098 days) | S3 | 5.5, 5.0.97, 5.1.69, 5.5.31, 5.7.1 | Linux (I only test it on ubuntu 11.10) | Any | SERVER_STATUS is always inited with SERVER_STATUS_AUTOCOMMIT=1 |
| 69661 | 2013-07-03 13:52 | 2013-07-03 15:15 | MySQL Workbench: SQL Editor | Not a Bug (3943 days) | S2 | 5.2.47 CE | Windows (XP SP3) | Any | Without autocommit turned on, SELECT statements don't refresh |
| 56878 | 2010-09-20 19:15 | 2015-12-17 17:27 | Connector / J | Can't repeat (3046 days) | S2 | 5.0.8, 5.1.13 | Windows (Server OS, client OS = any) | Any | Statement cancel method can sever connection |
| 83094 | 2016-09-22 9:40 | 2016-09-23 10:44 | MySQL Server | Not a Bug (2765 days) | S1 | 15.1 | Red Hat | Any | Auto-commit value getting changed at runtime |
| 87227 | 2017-07-27 18:00 | 2017-09-02 1:00 | MySQL Server: Documentation | No Feedback (2422 days) | S3 | 5.6 | Any | Any | Please clarify what happens when SETting AUTOCOMMIT while in BEGIN transaction |
| 95414 | 2019-05-19 4:40 | 2019-07-31 11:49 | MySQL Server: Documentation | Closed (1724 days) | S3 | 5.5,5.6,5.7,8.0 | Any | Any | Ambiguous statement about autocommit |
| 42565 | 2009-02-03 11:40 | 2021-04-29 15:51 | MySQL Cluster: Cluster (NDB) storage engine | Won't fix (1086 days) | S3 | Any | Any | ndb_cache_trans failure since SERVER_STATUS_IN_TRANS added to hash key | |
| 106435 | 2022-02-10 15:02 | 2022-04-06 21:53 | Connector / J | Closed (744 days) | S1 | 8.0.28 | Any | Any | 8.0.28 Connector/J has regressive in setAutoCommit after Bug#104067 (33054827) |
| 107875 | 2022-07-14 7:35 | 2022-12-19 12:52 | MySQL Server: C API (client library) | Verified (645 days) | S3 | 5.7 | Any | Any | SAVEPOINT created without an active transaction when autocommit=0 |
| 110535 | 2023-03-28 22:41 | 2023-10-10 9:17 | MySQL Server: SYS Schema | Closed (193 days) | S3 | 8.0.31, 8.0.32 | CentOS (7.9) | x86 (E5-2678 V3) | Mysql instance cannot be initialized correctly because autocommit is turned off. |
| Showing all 25 (Edit, Save, CSV, Feed) |
