Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Latest post by gneumann on Thursday, 03 August 2023 00:02 CDT
During Backup, a Warning appears:
You have database tables whose name starts with a form of the database prefix (jo_) which has a different letter case. This WILL cause problems if you restore your site on Windows or macOS. We strongly recommend excluding all tables which do not start with the configured prefix, exactly as shown above (case-sensitive).
All the previous backups the site did not mention that issue - any recommendation how to solve this? Any help welcome :-).
Regards
Gerd
This is a new warning, added last month.
Your site's database tables start with the prefix jo_ (lowercase letter j, followed by lowercase letter o, followed by an underscore). Akeeba Backup was told by MySQL that there are some tables whose names start with a variation of that, i.e. Jo_, jO_, or JO_. If you try restoring that backup on Windows or macOS you will get a problem due to a long-standing issue in MySQL itself as explained in https://www.akeeba.com/documentation/warnings/q106.html.
What you should do is explicitly stated in the message. I have written that message myself. I am really bad at paraphrasing myself.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Dear Nicholas,
thanks for the quick reply. As far as I understand the the warning text, the exclusion of all tables whose names do not begin with jo_ would be the solution? Unfortunately, the Database tables exclusion section does not list such files: There are no table names visible that start with i.e. Jo_, jO_, or JO_ :-(
Likewise, the Regex approach does not really get me anywhere: The Regular Expressions recipes for database tables in Akeeba Documentation do not mention the prefixes, unfortunately. What would you recommend?
Thanks for supporting!
Gerd
If you do not see any tables reported with those prefix variations you can ignore this error. There's always the chance that there was a false positive. This is very new code, there's always a chance it might misfire in some edge cases (detecting mixed case prefixes is far harder than it sounds because of the weird way MySQL handles table naming).
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
It is a wrong detection, see ticket 39301: https://www.akeeba.com/support/akeeba-backup/39301-database-prefix-issue-message.html
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Dear Nicholas,
I found also tables with different prefixes in the underlying database of our website.
Thank you for the quick support.
Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.
Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!