Closed WeT-Klb closed 2 years ago
The pma_*
tables with different encoding are not created by Baikal. They are from phpMyAdmin.
Is it safe to delete that pma-folder (on the left side of screenshot) inside the baikal-SQL-database?
I'm not sure. My guess would be that phpmyadmin then either re-creates them or stops working. For Baikal, these tables are irrelevant.
Ok - i tried and took the risk - everything works after i deleted those phpMyAdmin-related entries. phpMyAdmin has it´s own database and Baikal works like a charme, too. I still don´t have any idea why those entries took place inside Baikal´s database - but i guess maybe i did something wrong long time before.
But still one thing: All tables are utf8mb4_general_ci but "calendars" is the only one with utf8_unicode_ci. Is this ok or should it be the same like all other tables utf9mb4_general_ci?
That's indeed inconsistent in the default Baikal database. I will change the code, so it creates a utf9mb4_general_ci
encoded table in the future. Not sure what phpmyadmin does when changing the encoding.
Well - i changed everything to utf8mb through phpMyAdmin - and still everything works well.
I am using Baikal on a QNAP-NAS TS-251. The MySQL-Database is a mix of InnoDB and MyISAM. Also the different tables are a mix of different Collation like utf8mb4_general_ci, utf8_unicode_ci, utf8_bin. Are there any suggestion to change it to a homogene system?