[MDEV-28489] The Cyrillic string is not truncated by the number of characters when using the Connect Engine table Created: 2022-05-06 Updated: 2022-11-11 Resolved: 2022-11-11 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - Connect |
| Affects Version/s: | 10.5.9, 10.6.0 |
| Fix Version/s: | 10.11.2, 10.3.38, 10.4.28, 10.5.19, 10.6.12, 10.7.8, 10.8.7, 10.9.5, 10.10.3 |
| Type: | Bug | Priority: | Critical |
| Reporter: | long.skinny.boy | Assignee: | Andrew Hutchings |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | Connect-Engine, utf8 | ||
| Environment: |
CentOS 8 |
||
| Issue Links: |
|
||||||||
| Description |
|
Good afternoon, I previously used version 10.5.8 together with Connect Engine to display third-party information from other databases, there were no problems After that, I installed MariaDB 10.6.7 separately and I did the same thing and noticed one feature that now lines containing Cyrillic do not fit into the allotted number of characters. In other words, I have a string in MSSQL: ИВАНОВА When I created in MariaDB table with row VARCHAR(1) and get next: Change to VARCHAR(2) Change to VARCHAR(3) Change to VARCHAR(4) Change to VARCHAR(5) If row without cyrillic, only latin or numbers for example IVANOVA 10.5.8 = I Change to VARCHAR(2) Change to VARCHAR(3) It seems that he began to somehow divide the multibyte Cyrillic and other special characters |
| Comments |
| Comment by long.skinny.boy [ 2022-05-06 ] | ||||||||||||||||||
|
A simpler example that is easy to reproduce (JSON file):
At the output I get:
When I expect, and how it really is in 10.5.8
| ||||||||||||||||||
| Comment by long.skinny.boy [ 2022-05-07 ] | ||||||||||||||||||
|
It looks like this happened exactly between versions 10.5.8 and 10.5.9, also starting with 10.6.0 | ||||||||||||||||||
| Comment by Sergei Golubchik [ 2022-05-11 ] | ||||||||||||||||||
|
caused by these lines: https://github.com/MariaDB/server/blob/mariadb-10.5.9/storage/connect/ha_connect.cc#L1614-L1616 when removed, the bug goes away. | ||||||||||||||||||
| Comment by long.skinny.boy [ 2022-05-11 ] | ||||||||||||||||||
|
It's great that there is a solution! What is the probability that this can be fixed in the next 10.6.x release? As I understand it, this fix will also solve the problem of this issue : Or maybe you can somehow recompile this code file and create a certain hotfix? | ||||||||||||||||||
| Comment by long.skinny.boy [ 2022-10-18 ] | ||||||||||||||||||
|
Good afternoon, Sergei. Is the above described fix planned in new versions? Unfortunately, due to this error, I cannot upgrade to the latest version of MariaDB. Or maybe there is an opportunity to upgrade to the latest version, but leave ha_connect on the version from 10.5.8 release | ||||||||||||||||||
| Comment by Sergei Golubchik [ 2022-10-26 ] | ||||||||||||||||||
|
It's still work in progress, so I'm afraid it likely won't make it into this release |