Control: tags -1 moreinfo Hello!
pe 26. heinäk. 2019 klo 15.06 Otto Kekäläinen (o...@debian.org) kirjoitti: > > Hello! > > Thanks for reporting. I don't know it the MariaDB Connector C client > library reads and follows any settings in /etc/mysql/, we will need to > check that with upstream author if this is a bug or not. Seems Georg never replied to this, but now with MariaDB 10.5 in Debian unstable the situation is that 1) There is no charset defined for the client at all, only in server, which should be enough to force all new tables to be utf8mb4 anyway: # grep -rF utf /etc/mysql/ /etc/mysql/mariadb.conf.d/50-server.cnf:# utf8 4-byte character set. See also client.cnf /etc/mysql/mariadb.conf.d/50-server.cnf:character-set-server = utf8mb4 /etc/mysql/mariadb.conf.d/50-server.cnf:collation-server = utf8mb4_general_ci 2) Default connection status yields: # mariadb -Bse 'STATUS'; -------------- mariadb Ver 15.1 Distrib 10.5.5-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2 Connection id: 67 Current database: Current user: mysql@localhost SSL: Cipher in use is DHE-RSA-AES256-SHA Current pager: stdout Using outfile: '' Using delimiter: ; Server: MariaDB Server version: 10.5.5-MariaDB-1 Debian 10 Protocol version: 10 Connection: localhost via TCP/IP Server characterset: utf8mb4 Db characterset: utf8mb4 Client characterset: latin1 Conn. characterset: latin1 TCP port: 3306 If you Olaf want to contribute by improving this, I suggest you research upstream docs and configs and try to figure out if we actually need a full charset row of only utf8mb4 or if current situation is sufficient and the 'client' and 'conn' charset 'latin1' can be ignored. You Olaf could for example write an extension to our autopkgtest tests in Debian or the salsa-ci.yml to automatically test if some utf8mb4 thing works or now on each build/upload automatically.
