You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 1, 2022. It is now read-only.
Currently, a charset parameter present in any MySQL database configuration in config.yaml gets passed to the MySQL module where it's already supported.
I personally find this hidden feature useful because I often use utf8mb4.
I've also confirmed that setting the collate key to utf8mb4_general_ci or utf8mb4_unicode_ci doesn't change the default charset from utf8 to utf8mb4. Unless the charset is specifically set to utf8mb4, using either of utf8mb4_* collations will lead provisioning to fail.
From what I can tell, fully supporting this feature requires making only two changes:
Is there a reason this isn't officially supported that I'm not seeing? Is there more to fully implementing support than what I've outlined? Would you accept a pull request with these changes?
The text was updated successfully, but these errors were encountered:
Is there a reason this isn't officially supported that I'm not seeing?
Every module on puphpet has many more features than what's visible in the GUI. Adding all those options, though, would quickly make the GUI overwhelming.
I'd accept PRs, especially for something like this.
* Add `DB Charset` field to MySQL database configuration so a custom `charset` can be used.
* Renamed `DB Encoding` field to `DB Collation` for improved clarity.
Currently, a
charset
parameter present in any MySQL database configuration inconfig.yaml
gets passed to the MySQL module where it's already supported.I personally find this hidden feature useful because I often use
utf8mb4
.I've also confirmed that setting the
collate
key toutf8mb4_general_ci
orutf8mb4_unicode_ci
doesn't change the defaultcharset
fromutf8
toutf8mb4
. Unless thecharset
is specifically set toutf8mb4
, using either ofutf8mb4_*
collations will lead provisioning to fail.From what I can tell, fully supporting this feature requires making only two changes:
In
src/PuphpetBundle/Resources/config/mysql/defaults.yml
, change:To:
And in
src/PuphpetBundle/Resources/views/mysql/database.html.twig
, add:Is there a reason this isn't officially supported that I'm not seeing? Is there more to fully implementing support than what I've outlined? Would you accept a pull request with these changes?
The text was updated successfully, but these errors were encountered: