Error Code: 2013. Lost connection to MySQL server during query
Today, when using the official MySQL graphical tool mysqlworkbench to query the view, this error is reported:
error code: 2013 Lost connection to MySQL server during query
If the disk is not full, you can use the following method:
Modify the timeout in the red box. The default is 10 seconds. If the table data is too large and the query time is too long, the above error will be returned.
Read More:
- (Fixed) workbench MySQL Error Code: 2013. Lost connection to MySQL server during query
- Remote connection to MySQL database error: is not allowed to connect to this MYSQL server solution
- General error: 2006 MySQL server has gone away [How to Solve]
- [Solved] EOS7.6 Error: Init DB failed [Specified key was too long; max key length is 767 bytes…
- MySQL server has gone away Error [How to Solve]
- [Solved] MySQL connection error: communications link failure
- MySQL character set error resolution: err=Error 3988: Conversion from collation utf8mb4_unicode_ci into utf8_general_ci impo
- Solve ERROR 1231 (42000): Variable’time_zone’ can’t
- Docker: How to Solve MYSQL8 & Navicat remote connection error
- MySQL 8.0 error 1114 (HY000): the table’sbtest1’is full (Fixed)
- [Solved] com.mysql.jdbc.MysqlDataTruncation: Data truncation xxxx
- Mysql8.02/ubuntu 20 ERROR 1449 (HY000) [How to Solve]
- Idea connect mysql error Server returns invalid timezone. Go to’Advanced’ tab and set’serverTimezone’ property
- How to Solve mysql [Err] 1067-Invalid default value for
- [Solved] Sequelize DatabaseError: ER_WRONG_FIELD_WITH_GROUP: Expression #2 of SELECT list is not in GROUP
- [Solved]ERROR 1067 (42000): Invalid default value for ‘end_time‘ Mysql
- [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata
- [Solved] There is a problem with mysql8.0 without password in Navicat connection
- Mysql5.7.18.1 Error 1054 (42S22): Unknown Column’password’ In’field List’ When Changing User Password
- [MySQL] mysql 5.5 and 5.6 timestamp default default value CURRENT_TIMESTAMP problem