The Ultimate Guide to High Availability with MariaDB

Comments - Adding a latin name to a larin1 column works on 10.4, doesn't work on 10.5

 
2 years, 10 months ago Alexander Barkov
Re: Adding a latin name to a larin1 column works on 10.4, doesn't work on 10.5

Latin Small Letter L with Stroke does not exists in latin1.

MariaDB can do two things when an impossible character gets written to a column:

- Issue a warning (the character gets replaced to the question mark in this case)

- Issue an error

The choice between the warning and the error is made according to:

- STRICT_TRANS_TABLES flag in sql_mode

- STRICT_ALL_TABLES flag in sql_mode

- The engine used.

It seems that after switch from 10.4 to 10.5 either of them have changed.

Please check the output of this script in both installations:

SELECT @@sql_mode;
SHOW CREATE TABLE <tablename>;
 
2 years, 10 months ago Marko Mäkelä
Re: Adding a latin name to a larin1 column works on 10.4, doesn't work on 10.5 [Answer]

The MariaDB encoding name "latin1" refers to Microsoft Code Page 1252, which extends ISO 8859-1 (a.k.a. ISO Latin 1) with a few code points.

The \xC5\x82 in your output looks like UTF-8 for U+0142 to me. The 0x82 is not a valid code point in "latin1" encoding. 0xc5 would be interpreted as U+00C5 LATIN CAPITAL LETTER A WITH RING ABOVE.

So, it looks like in 10.5 some additional validation was implemented. Previously, the incorrect data was wrongly and silently accepted. You could get surprising results for ORDER BY when using the wrong encoding and collation.

I think that you should define the table with the utf8mb3 or utf8mb4 encoding if you are going to insert UTF-8 encoded data into it.

 
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.