[MDEV-4118] Merge Unicode command line client from 5.6 Created: 2013-01-30  Updated: 2023-10-30  Resolved: 2022-08-17

Status: Closed
Project: MariaDB Server
Component/s: Scripts & Clients
Fix Version/s: N/A

Type: Task Priority: Minor
Reporter: Alexander Barkov Assignee: Unassigned
Resolution: Duplicate Votes: 2
Labels: unicode

Issue Links:
Duplicate
duplicates MDEV-26713 Windows - improve i18n support Closed

 Description   

MySQL 5.6 implemented Unicode support in command line client (mysql.exe).

Earlier mysql.exe versions support only OEM (DOS) locale character set
(e.g. cp850 on a Western machine), which is old fashioned:
it does not support neither Euro sign nor modern punctuation characters.

This feature needs to be merged from MySQL.

 Comments   
Comment by Daniël van Eeden [ 2015-10-17 ]

Isn't the mysql.exe the same? I thought it starts a cmd.exe with unicode support and then calls mysql.exe with default-character-set=utf8 (or mysql.exe detects the unicode support of the cmd.exe and switches automatically).

Please try to use utf8mb4 instead of utf8 when implementing this feature.

There could be more things needed for Unicode support on Windows. With powershell this won't work:
mysqldump.exe -A > dump.sql
mysql.exe < dump.sql
This is because the stream will be converted to utf16 by powershell and mysql.exe can't handle utf16....
https://bugs.mysql.com/bug.php?id=73481
https://bugs.mysql.com/bug.php?id=73672

Comment by Vladislav Vaintroub [ 2022-08-17 ]

Already solved in MDEV-26713 .

dveeden, there are various workarounds for powershell to reading the raw input/output redirections, by favorite being prepending command line with "cmd /c "

Generated at Thu Feb 08 06:53:53 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.