[MDEV-26163] after 10.6 upgrade problems connecting to pipo db Created: 2021-07-16  Updated: 2021-08-18  Resolved: 2021-08-18

Status: Closed
Project: MariaDB Server
Component/s: Character Sets
Affects Version/s: 10.6.3
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Daniel Komkommer Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: need_feedback

Attachments: PNG File WheatherBot crash MariaDB 10.6.png    
Issue Links:
Duplicate
is duplicated by MDEV-26105 MariaDB 10.6 cannot be used from C# c... Closed
Problem/Incident
is caused by MDEV-8334 Rename utf8 to utf8mb3 Closed

 Description   

Hi I was looking to the specifics of mariadb server on windows server.
I was running version 10.5 and upgraded to 10.6 about a week ago.
I'm running 10.6 on Windows Server 2019 as a research WIMP environment.
Since the upgrade to 10.6 I'm having problems reading some data on the clients.
These clients are Windows iot devices with an UWP batch program that gathers and uploads weather data to my MariaDB.
It seems some crashes occur related to the character set although I have not changed anything except the database version upgrade.

 Comments   
Comment by Sergei Golubchik [ 2021-07-16 ]

This was also reported as MDEV-26105.

There are few things you can do:

  • report a bug at bugs.mysql.com that mysql-connector-net doesn't support utf8mb3 character set
  • use a different .net connector, if possible.
  • configure all configurable character sets to be not utf8, or
  • put old-mode= into your my.cnf, so that utf8 would mean utf8mb4 that mysql-connector-net knows
  • if you have tables in the utf8mb3 charset — you might need to alter them to utf8mb4
Comment by Daniel Komkommer [ 2021-07-16 ]

Hallo Sergei,

put old-mode= into your my.cnf, so that utf8 would mean utf8mb4 that mysql-connector-net knows

Where can I do that on a Windows Server 2019 MariaDB installation?

Comment by Sergei Golubchik [ 2021-07-17 ]

Sorry, on Windows it's usually called my.ini, look for that name instead.

Generated at Thu Feb 08 09:43:13 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.