The base was moved from the hospital (5.7.10, win7), where everything works fine, on a laptop (5.7.11, win10). Screenshot of how this looks attached. I transferred the base by simply copying the database folder to the / data folder, if that matters. What it looks like in the console

enter image description here

  • And this table is not InnoDB? - tutankhamun
  • show result SHOW CREATE TABLE users - tutankhamun
  • @tutankhamun Attached to the question. - Mokridze
  • You are mistaken. Need SHOW CREATE TABLE users and not just CREATE TABLE users - tutankhamun
  • Whatever, the error is the same. - Mokridze

1 answer 1

Reply from comments

This situation often occurs when you transfer table frm files manually, while the table data remains in the InnoDB tablespace. It is better not to transfer databases by copying files. Although MyISAM tables allow this, at this point the server should either be stopped or the tables locked (for example, using the mysqlhotcopy utility).

The most reliable way to migrate a database is to create a SQL dump.

 mysqldump -u root -p dbname > dbname.sql

then deployed to the target server

 mysql -u root -p dbname < dbname.sql

Here root is the name of the MySQL user, dbname is the name of the database, dbname.sql is the name of the SQL dump file