Mysql Mariadb自动增量删除所有记录后重置
当我从mysql表中删除所有记录时，自动递增计数器被重置为0。我的应用程序逻辑是将记录从MySQL迁移到其他分析引擎，然后从MySQL中删除迁移的记录。分析引擎使用与MySQL相同的主键管理记录，因此当MySQL重置计数器时，我的分析引擎中出现重复键错误。我希望Mysql保留自动增量，即使我从数据库中删除了所有记录Mysql Mariadb自动增量删除所有记录后重置,mysql,mariadb,auto-increment,Mysql,Mariadb,Auto Increment,当我从mysql表中删除所有记录时，自动递增计数器被重置为0。我的应用程序逻辑是将记录从MySQL迁移到其他分析引擎，然后从MySQL中删除迁移的记录。分析引擎使用与MySQL相同的主键管理记录，因此当MySQL重置计数器时，我的分析引擎中出现重复键错误。我希望Mysql保留自动增量，即使我从数据库中删除了所有记录 alter table test auto_increment = 100; 我可以在删除记录后执行上述查询以保留自动增量，但如果重新启动MySQL，该计数器将再次重置为默认值0
alter table test auto_increment = 100;
MariaDB [MY_DB]> SHOW TABLE STATUS FROM `MY_DB` WHERE `name` LIKE 'test' ;
+---------+--------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+-----------+----------+----------------+---------+
| Name | Engine | Version | Row_format | Rows | Avg_row_length | Data_length | Max_data_length | Index_length | Data_free | Auto_increment | Create_time | Update_time | Check_time | Collation | Checksum | Create_options | Comment |
+---------+--------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+-----------+----------+----------------+---------+
| test | InnoDB | 10 | Compact | 6 | 2730 | 16384 | 0 | 0 | 0 | 7 | 2017-05-22 23:38:06 | NULL | NULL | utf8_bin | NULL | | |
+---------+--------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+-----------+----------+----------------+---------+
1 row in set (0.00 sec)
MariaDB [MY_DB]> select max(id) from test;
+---------------+
| max(id) |
+---------------+
| 6 |
+---------------+
1 row in set (0.00 sec)
MariaDB [MY_DB]> delete from test where id in (1,2,3,4,5,6);
Query OK, 6 rows affected (0.00 sec)
MariaDB [MY_DB]> SHOW TABLE STATUS FROM `MY_DB` WHERE `name` LIKE 'test' ;
+---------+--------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+-----------+----------+----------------+---------+
| Name | Engine | Version | Row_format | Rows | Avg_row_length | Data_length | Max_data_length | Index_length | Data_free | Auto_increment | Create_time | Update_time | Check_time | Collation | Checksum | Create_options | Comment |
+---------+--------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+-----------+----------+----------------+---------+
| test | InnoDB | 10 | Compact | 0 | 0 | 16384 | 0 | 0 | 0 | 7 | 2017-05-22 23:38:06 | NULL | NULL | utf8_bin | NULL | | |
+---------+--------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+-----------+----------+----------------+---------+
1 row in set (0.00 sec)
MariaDB [MY_DB]> exit
Bye
root@atd-3000:~# systemctl restart mariadb
root@atd-3000:~# mysql -p***** MY_DB;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 57
Server version: 10.1.17-MariaDB MariaDB Server
Copyright (c) 2000, 2016, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [MY_DB]> SHOW TABLE STATUS FROM `MY_DB` WHERE `name` LIKE 'test' ;
+---------+--------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+-----------+----------+----------------+---------+
| Name | Engine | Version | Row_format | Rows | Avg_row_length | Data_length | Max_data_length | Index_length | Data_free | Auto_increment | Create_time | Update_time | Check_time | Collation | Checksum | Create_options | Comment |
+---------+--------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+-----------+----------+----------------+---------+
| test | InnoDB | 10 | Compact | 0 | 0 | 16384 | 0 | 0 | 0 | 1 | 2017-05-22 23:38:06 | NULL | NULL | utf8_bin | NULL | | |
+---------+--------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+-----------+----------+----------------+---------+
DELETEAUTO_INCREMENTTRUNCATEDELETEAUTO_INCREMENTTRUNCATE另一方面，drop查询只删除表&不创建新表；因此，自动增量id保持不变。实际上，truncate query首先完全删除表，然后创建一个空白表。。。因为它现在是一个全新的表，所以自动增量id被重置为1
另一方面，drop查询只删除表&不创建新表；因此，自动增量id保持不变。由于innodb是基于内存的计数器，innodb不会保留自动增量值。我已经实施了一个解决方案：
希望它能帮助其他面临同样问题的人。由于innodb是基于内存的计数器，innodb不会保留自动增量值。我已经实施了一个解决方案：
希望它能帮助其他面临同样问题的人。DELETE query不会重置自动增量id，而TRUNCATE将发布用于删除所有迁移行的查询。您是对的。但是如果重新启动mysql，它会将自动增量计数器重置回1。下面是我正在使用的删除查询：
delete from test where id in（1,2,3,4,5）delete from test where id in（1,2,3,4,5）MAX（id）MAX（id）