Bug? #1146 - Table 'xxx.xxxxx' doesn't exist

前端 未结 18 1718
春和景丽
春和景丽 2020-11-29 05:49

I am using windows XP. I am creating a table in phpMyAdmin using its built-in create table feature, my database name is ffffd.

It generates the following

相关标签:
18条回答
  • 2020-11-29 06:12

    Restarting MySQL works fine for me.

    0 讨论(0)
  • 2020-11-29 06:13

    Today i was facing same problem. I was in very difficult situation but what id did i create a table with diffrent name e.g (modulemaster was not creating then i create modulemaster1) and after creating table i just do the rename table.

    0 讨论(0)
  • 2020-11-29 06:14

    Check filenames.
    You might need to create a new database in phpmyadmin that matches the database you're trying to import.

    0 讨论(0)
  • 2020-11-29 06:18

    I had the same issue. It happened after windows start up error, it seems some files got corrupted due to this. I did import the DB again from the saved script and it works fine.

    0 讨论(0)
  • 2020-11-29 06:20

    Recently I had same problem, but on Linux Server. Database was crashed, and I recovered it from backup, based on simply copying /var/lib/mysql/* (analog mysql DATA folder in wamp). After recovery I had to create new table and got mysql error #1146. I tried to restart mysql, and it said it could not start. I checked mysql logs, and found that mysql simply had no access rigths to its DB files. I checked owner info of /var/lib/mysql/*, and got 'myuser:myuser' (myuser is me). But it should be 'mysql:adm' (so is own developer machine), so I changed owner to 'mysql:adm'. And after this mysql started normally, and I could create tables, or do any other operations.

    So after moving database files or restoring from backups check access rigths for mysql.

    Hope this helps...

    0 讨论(0)
  • 2020-11-29 06:20

    For me it was a table name upper/lower case issue. I had to make sure that table case name matched in a delete query, table notifications was not the same as Notifications. I fixed it by matching table name case with query and what MySQLWorkbench reported.

    What is wierd is that this error showed up in a worked sql statement. Don't know what caused this case sensitivity. Perhaps an auto AWS RDS update.

    0 讨论(0)
提交回复
热议问题