There are 7 comments.
 
 
XWiki Docker images / cid:jira-generated-image-avatar-31afacb1-fcb9-4f3b-a39f-b00e0f9b3552 XDOCKER-342 Closed

Document using MySQL with utf8mb4 by using docker-compose

 
View issue   ·   Add comment
 

7 comments

 
cid:jira-generated-image-avatar-4b17afb5-4bdd-4e50-9898-0082e632f080 Vincent Massol on 19/Jul/26 10:45
 
{{ utf8mb4 }} is already the default charset/collation for both MySQL and MariaDB in the docker \ -compose setup \- it 's is set via \ {{ - \ -character \ -set \ -server=utf8mb4 }} / \ {{ - \ -collation \ -server= utf8mb4\_bin utf8mb4_bin}} in the {{ command: }} section of the generated {{ docker \ -compose.yml }} files. This has been the case since XDOCKER \ -285 \ (Nov 2023 \ ), which predates this issue. The downloadable {{ docker \ -compose.yml }} files therefore already produce a {{ utf8mb4 }} database out of the box, so no documentation change is needed.
 
cid:jira-generated-image-avatar-4b17afb5-4bdd-4e50-9898-0082e632f080 Vincent Massol on 19/Jul/26 10:45
 
{{utf8mb4}} is already the default charset/collation for both MySQL and MariaDB in the docker-compose setup — it is . The generated {{docker-compose.yml}} files set via it in the DB service 's {{ command:}} section:

{code}
--character-set-server=utf8mb4 }} / {{
--collation-server=utf8mb4_bin }} in the
{ {command: code } } section of the generated {{docker-compose.yml}} files.

This has been the case since XDOCKER-285 (Nov 2023), which predates this issue . The , so the downloadable {{docker-compose.yml}} files therefore already produce a {{utf8mb4}} database out of the box , so and no documentation change is needed.
 
cid:jira-generated-image-avatar-4b17afb5-4bdd-4e50-9898-0082e632f080 Vincent Massol on 19/Jul/26 10:46
 
{{utf8mb4}} is already the default charset/collation for both MySQL and MariaDB in the docker-compose setup. The In the generated {{docker-compose.yml}} files set it in , the DB service 's {{command:}} section :

sets { code}
--
{ character-set-server=utf8mb4
--
}} and {{ collation-server=utf8mb4_bin
{code
}

}. This has been the case since XDOCKER-285 (Nov 2023), which predates this issue, so the downloadable {{docker-compose.yml}} files already produce a {{utf8mb4}} database out of the box and no documentation change is needed.
 
cid:jira-generated-image-avatar-4b17afb5-4bdd-4e50-9898-0082e632f080 Vincent Massol on 19/Jul/26 10:47
 
{{utf8mb4}} is already the default charset/collation for both MySQL and MariaDB in the docker-compose setup. In the generated {{docker-compose.yml}} files, the DB service {{command:}} section sets {{character-set-server=utf8mb4}} and {{collation-server=utf8mb4_bin}}. This has been the case since Fixed by XDOCKER-285 (Nov 2023), which predates this issue, so the downloadable {{docker-compose.yml}} files already produce a {{utf8mb4}} database out of the box and no documentation change is needed .
 
cid:jira-generated-image-avatar-4b17afb5-4bdd-4e50-9898-0082e632f080 Vincent Massol on 19/Jul/26 10:47
 
Uses {{utf8mb4}} charset. Fixed by XDOCKER-285 already.
 
cid:jira-generated-image-avatar-4b17afb5-4bdd-4e50-9898-0082e632f080 Vincent Massol on 19/Jul/26 10:47
 
Uses {{ utf8mb4 utf8mb4_bin }} charset collation . Fixed by XDOCKER-285 already.
 
cid:jira-generated-image-avatar-4b17afb5-4bdd-4e50-9898-0082e632f080 Vincent Massol on 19/Jul/26 10:47
 
Uses {{ utf8mb4_bin utf8mb4 }} is already the default charset/ collation for both MySQL and MariaDB in the docker-compose setup . Fixed by The generated {{docker-compose.yml}} files set it in the DB service {{command:}} section:

{code}
--character-set-server=utf8mb4
--collation-server=utf8mb4_bin
{code}

This has been the case since
XDOCKER-285 (Nov 2023), which predates this issue, so the downloadable {{docker-compose.yml}} files already produce a {{utf8mb4}} database out of the box and no documentation change is needed .