Uncaught mysqli_sql_exception: Function or expression ‘AUTO_INCREMENT’ cannot be used in the USING HASH clause of id in /home/
I never encountered this, everything worked well with my database and now one of the table, user, shows up like this and cannot be accessed.
I had a look at what the “in use” part could mean.
I think it means it’s a database view. A view is a sort-of table, but one that doesn’t actually have data. But you can query it like it’s a table, which is then mapped to actual tables by the code of the view.
If you want user to be an actual table, you will need to delete/drop the view, and create a new table instead.
The table was full, how did it get empty 
I had all my users stored in it, maybe some hack or a glitch?
Any way to get it back or was it my job to make a backup as it is a free service?
That’s how all the tables look like :
PS : I don’t really care about data iself but the way the table was built, yes.
I believe this is a coding issue rather than hosting issue though. The error message clearly suggest that you cannot use AUTO_INCREMENT when using hashed values.
I don’t know why does it worked before though.
@Admin — I believe that a view doesn’t look like that in phpMyAdmin. The “in use” message probably suggest something else.
The code worked well --in fact it had been working well for over a year–, then I did not touch anything for 2 weeks and when I attempted to log into my website I had that error.
There was some database maintenance yesterday. I know it wasn’t completely smooth, but I was not aware of it having caused data corruption issues. But I have the suspicion that this issue might be related.
I will have to check with iFastNet what’s actually going on and see what can be done to recover the table(s) affected by this.
I got a reply of what this issue was about.
I turns out that your table was using some features that broke following the update done yesterday. Apparently, it had some special options on the UNIQUE constraint on the table that broke the table when updating.
iFastNet staff has managed to recover your table, but needed to make some changes to the key to make it possible to import it. So the table is there, but not exactly as you left it. So please check the definition of the unique constraint to make sure that it still does what you want it to do.
Many thanks to you and iFastNet ! My database was successfully restored! 
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
