Tables Are Not Being Set to the Desired Collation #528

shefik opened this Issue Oct 11, 2012 · 4 comments


None yet

2 participants


Prior to executing a clean install of Zikula, an empty MySQL database might already be set to the desired collation "utf8_unicode_ci". However, during the install process, the tables always get created to the collation "utf8_general_ci", when it might be desired to set the collation to "utf8_unicode_ci" instead.



what is the desired collation? utf8_unicode_ci or utf8_general_ci


We've always been using utf8_general_ci


I think this not a bug. For me it looks like everything is working like it is supposed.

I think it is features request, to support other collations. @shefik Or did I understood you wrong?

Is there a reason why we should support other collations next to utf8_general_ci?


I think the issue if you must create the database manually, and it should be created as UTF8. I also do not believe this is a bug.

@ghost ghost closed this Sep 8, 2013
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment