Page 1 of 1
Umlauts with backup/restore
Posted: 2021-07-15 17:05
by SkayyHH
Hello everybody,
I have a problem with the appgini database backup and restore function. If I make a database backup using the appgini backup function and then restore the data from the backup, my umlauts are not displayed correctly. They are ok before the backup. Example:
Before the backup: Müller
After restoring: Müller
Can someone tell me what I have to do so that the sql dump stores the umlauts correctly? Database ist UTF-8.
Thank you very much, Kai
Re: Umlauts with backup/restore
Posted: 2021-07-15 18:09
by SkayyHH
Addition:
Character encoding in AppGini is "Unicode UTF8", "Don´t enforce MySQL encoding" ist not selected (will not help)
Character encoding in MySQL Database is "UTF8_general_ci"
Thanks much, Kai
Re: Umlauts with backup/restore
Posted: 2021-07-17 22:09
by SkayyHH
Solved. Works with utf8mb4_general_ci.
Re: Umlauts with backup/restore
Posted: 2021-07-17 22:31
by SkayyHH
Not full solved
Now the correct umlauts are in the dump backup file. But if i restore from backup the umlauts are not right again in the database.
Any ideas?
Thanks much, Kai
Re: Umlauts with backup/restore
Posted: 2021-07-17 22:57
by SkayyHH
It seems to be a bug in the appgini backup / restore script.
When I create an sql dump via the appgini backup, the umlauts in the dump are displayed correctly.
If I use the appgini backup / restore tool to restore from the backup, the umlauts are no longer displayed correctly.
When I import the dump created by appgini into my database via phpmyadmin, the umlauts are displayed correctly.
Thanks for the help, Kai
Re: Umlauts with backup/restore
Posted: 2021-07-19 13:05
by a.gneady
Hmm ... I'll inspect this issue and try to make a fix for it. Please run this query in phpMyAdmin and let me know the output:
Code: Select all
SELECT `DEFAULT_COLLATION_NAME` FROM `information_schema`.`SCHEMATA` WHERE `SCHEMA_NAME`='YOUR_DB_NAME';
Replace
YOUR_DB_NAME above with the actual database name.
Re: Umlauts with backup/restore
Posted: 2021-07-20 05:44
by SkayyHH
Hi Ahmed,
thank you very much for your support!
I get this info displayed. Is that what you need?
Code: Select all
DEFAULT_COLLATION_NAME
utf8_general_ci
latin1_swedish_ci
latin1_swedish_ci
latin1_swedish_ci
utf8_general_ci
utf8_general_ci
latin1_swedish_ci
utf8_unicode_ci
latin1_swedish_ci
latin1_swedish_ci
latin1_swedish_ci
Many greetings,
Kai
Re: Umlauts with backup/restore
Posted: 2021-07-20 10:42
by SkayyHH
And here is a screenshot of the database structure:
Re: Umlauts with backup/restore
Posted: 2021-07-26 12:41
by a.gneady
Hmm .. different tables are using different collations ... this is not an optimum setting, but I'll investigate this issue and see how to fix it.
Re: Umlauts with backup/restore
Posted: 2021-07-27 08:56
by SkayyHH
Hello Ahmed,
sorry. Your select did not work for me at first. I had all the collations in my database displayed. Here is another current screenshot. This is right so.
I've tried utf8mb4_general_ci and utf8_general_ci and a few others. However, I cannot restore it without the umlauts being displayed incorrectly. Direct import works well.
Many greetings, Kai
Re: Umlauts with backup/restore
Posted: 2021-08-21 04:16
by SkayyHH
Hello, everyone,
can any of you confirm this? Or does the restore work for you with umlauts?
Thanks much, Kai