Skip to content

Supported collations and character sets

By default, DB_COLLATE is defined as utf8mb4_unicode_ci on the VIP Platform’s MariaDB databases. Only the following collations are supported by utf8mb4 and can be used in SQL files for import:

| utf8mb4_general_ci           |
| utf8mb4_bin                  | 
| utf8mb4_unicode_ci           | 
| utf8mb4_icelandic_ci         | 
| utf8mb4_latvian_ci           | 
| utf8mb4_romanian_ci          | 
| utf8mb4_slovenian_ci         | 
| utf8mb4_polish_ci            | 
| utf8mb4_estonian_ci          | 
| utf8mb4_spanish_ci           | 
| utf8mb4_swedish_ci           | 
| utf8mb4_turkish_ci           | 
| utf8mb4_czech_ci             | 
| utf8mb4_danish_ci            | 
| utf8mb4_lithuanian_ci        | 
| utf8mb4_slovak_ci            | 
| utf8mb4_spanish2_ci          | 
| utf8mb4_roman_ci             | 
| utf8mb4_persian_ci           | 
| utf8mb4_esperanto_ci         | 
| utf8mb4_hungarian_ci         | 
| utf8mb4_sinhala_ci           | 
| utf8mb4_german2_ci           | 
| utf8mb4_croatian_mysql561_ci | 
| utf8mb4_unicode_520_ci       | 
| utf8mb4_vietnamese_ci        | 
| utf8mb4_croatian_ci          | 
| utf8mb4_myanmar_ci           | 
| utf8mb4_thai_520_w2          | 
| utf8mb4_general_nopad_ci     | 
| utf8mb4_nopad_bin            | 
| utf8mb4_unicode_nopad_ci     | 
| utf8mb4_unicode_520_nopad_ci | 

Supported character sets

By default, DB_CHARSET is defined as utf8mb4 on the VIP Platform’s MariaDB databases. It is recommended that SQL files for import use the utf8mb4 character set in order to avoid unexpected issues.

Tables created with the utf8 charset are compatible, but should be avoided due to their inability to store 4-byte characters (e.g., emojis, musical symbols).

Last updated: May 27, 2022