New problem with database tables being InnoDB

Open to all! Ask other shopowners for help.
Post Reply
14Steve14
Senior Contributor
Posts: 923
Joined: Fri Oct 25, 2019 7:01 pm
Phoenix Version: v1.0.9.1
Has thanked: 17 times
Been thanked: 103 times

New problem with database tables being InnoDB

Post by 14Steve14 »

Forgot to mention this is my current site running on phoenix version 1.7.11.

For some reason this morning all my orders totals have a question mark ? instead of a £ Pound sign.

Looking in the currencies admin area the symbol had been changed to the ? mark, but when I changed it back to a £ sign nothing changed. I tried changing it to &pound but that didn't change anything.

When trying to check the database I get a message in phpmyadmin saying 'The storage engine for the table doesn't support r...' which I think is to do with the database table being set as InnoDB rather than MyISAM which apparently can be repaired.

Should it be that? If so how do you repair and check a database table.


Join The Code Co-op to get access to your library in the Code Co-op Forum
14Steve14
Senior Contributor
Posts: 923
Joined: Fri Oct 25, 2019 7:01 pm
Phoenix Version: v1.0.9.1
Has thanked: 17 times
Been thanked: 103 times

Re: New problem with database tables being InnoDB

Post by 14Steve14 »

For now I have changed the ? for £ sign in the database so at least we can print off todays invoices. I am just a bit concerned about what happened so have opened a support ticket with the host to see if they can shed any light on why things may have changed as it was all working yesterday, and I did nothing to alter anything.
ecartz
Core Team
Posts: 3084
Joined: Tue Nov 05, 2019 6:02 pm
Phoenix Version:
Has thanked: 4 times
Been thanked: 208 times

Re: New problem with database tables being InnoDB

Post by ecartz »

You don't need to repair an InnoDB table. The thing that gets "repaired" with MyISAM isn't a problem for InnoDB. This would tend to be an encoding problem somewhere.

https://stackoverflow.com/a/39432636/6660678 seems like a good set of things to check. Note that the other answer to the same question wouldn't apply here, as we already do that.
14Steve14
Senior Contributor
Posts: 923
Joined: Fri Oct 25, 2019 7:01 pm
Phoenix Version: v1.0.9.1
Has thanked: 17 times
Been thanked: 103 times

Re: New problem with database tables being InnoDB

Post by 14Steve14 »

ecartz wrote: Wed Aug 24, 2022 11:06 am You don't need to repair an InnoDB table. The thing that gets "repaired" with MyISAM isn't a problem for InnoDB. This would tend to be an encoding problem somewhere.

https://stackoverflow.com/a/39432636/6660678 seems like a good set of things to check. Note that the other answer to the same question wouldn't apply here, as we already do that.
@ecartz Thanks for that. On further investigation I read somewhere that I didn't need to repair the database as it was InnoDB.

After updating the currency that was for some reason changed most of the £ sign returned. That just left the most recent 400 or so pages that were wrong. I tried all other incarnations of the £ sign and nothing worked so in the end I used sql to change the ? to a £ sign and all seems to be right now.

New orders, and three test orders all seem to be going through as they should. It looks like its time to get on and updated the site to the latest version which may sort a few other errors out that slowly appear on the site. Test site seems to run well on the supplied data so its really a case of just uploading the files, adding hundreds of addons and transferring the data. Sounds easy if you say it quick.


Join The Code Co-op to get access to your library in the Code Co-op Forum
Post Reply