• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved collation_database

dyrer

Basic Pleskian
+--------------------------+--------------------+
| Variable_name | Value |
+--------------------------+--------------------+
| character_set_client | utf8mb4 |
| character_set_connection | utf8mb4 |
| character_set_database | utf8 |
| character_set_filesystem | binary |
| character_set_results | utf8mb4 |
| character_set_server | utf8mb4 |
| character_set_system | utf8 |
| collation_connection | utf8mb4_unicode_ci |
| collation_database | utf8_general_ci |
| collation_server | utf8mb4_unicode_ci |
+--------------------------+--------------------+

Hi
How can also switch collation_database to utf8mb4_unicode_ci
 
Note, that utf8mb4 Character Set (4-Byte UTF-8 Unicode Encoding) support is available starting from the MySQL 5.5.3 version.
'utf8mb4_unicode_520_ci' collation present by default there.
 
That's strange. I just imported a database that used utf8mb4 into a Maria DB 10.1. Maybe the software manufacturer of the application can help to identify what's wrong? I doubt that this is a database issue.
 
systemctl list-unit-files | grep enabled | grep -iE '(sql|db)'


Code:
mariadb.service                          enabled
mysql.service                            enabled
mysqld.service                           enabled

Is this correct running three services?
 
I had to add into /etc/mysql/conf.d/my.cnf

Code:
[mysqld]
innodb_large_prefix=true
innodb_file_format=barracuda
innodb_file_per_table=true


my complete my.cnf is
Code:
[client]
default-character-set = utf8mb4

[mysql]
default-character-set = utf8mb4

[mysqld]
init-connect='SET NAMES utf8mb4'
collation_server=utf8mb4_unicode_ci
character_set_server=utf8mb4
skip-character-set-client-handshake

innodb_large_prefix=true
innodb_file_format=barracuda
innodb_file_per_table=true
 
Yes solved.
No needed to add utfmb8, is my preference
This solves problem for Drupal, and Backdrop CMS (is a drupal fork)
 
Back
Top