diff options
| author | unknown <heikki@hundin.mysql.fi> | 2005-09-04 13:00:03 +0300 |
|---|---|---|
| committer | unknown <heikki@hundin.mysql.fi> | 2005-09-04 13:00:03 +0300 |
| commit | d6b70bf4aeee0bfbb74a2ae6a3d7e8617531b1b7 (patch) | |
| tree | 78bb9c92be6614ca02966462c69f298f2546aaf5 /sql/ha_innodb.cc | |
| parent | 53379f982d30d7f2f21077e341f5eacdedf854ef (diff) | |
| download | mariadb-git-d6b70bf4aeee0bfbb74a2ae6a3d7e8617531b1b7.tar.gz | |
ha_innodb.cc:
Better comments about auto-inc and SHOW TABLE STATUS
sql/ha_innodb.cc:
Better comments about auto-inc and SHOW TABLE STATUS
Diffstat (limited to 'sql/ha_innodb.cc')
| -rw-r--r-- | sql/ha_innodb.cc | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/sql/ha_innodb.cc b/sql/ha_innodb.cc index df21d82bb77..75348d39208 100644 --- a/sql/ha_innodb.cc +++ b/sql/ha_innodb.cc @@ -5543,7 +5543,7 @@ ha_innobase::info( /* The following function call can the first time fail in a lock wait timeout error because it reserves the auto-inc - lock on the table. If it fails, then someone has already inited + lock on the table. If it fails, then someone is already initing the auto-inc counter, and the second call is guaranteed to succeed. */ @@ -6893,9 +6893,11 @@ func_exit: func_exit_early: /* Since MySQL does not seem to call autocommit after SHOW TABLE - STATUS (even if we would register the trx here), we must commit our + STATUS (even if we would register the trx here), we commit our transaction here if it was started here. This is to eliminate a - dangling transaction. */ + dangling transaction. If the user had AUTOCOMMIT=0, then SHOW + TABLE STATUS does leave a dangling transaction if the user does not + himself call COMMIT. */ if (trx_was_not_started) { |