Bug 223463 - databases/mysql56-client: mysql CLI does not allow to input non-ascii (Cyrillic) characters
Summary: databases/mysql56-client: mysql CLI does not allow to input non-ascii (Cyrill...
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Jochen Neumeister
Keywords: needs-qa
Depends on:
Reported: 2017-11-06 06:47 UTC by Victor Sudakov
Modified: 2020-05-24 09:24 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (mmokhi)


Note You need to log in before you can comment on or make changes to this bug.
Description Victor Sudakov 2017-11-06 06:47:14 UTC
I have LANG=ru_RU.UTF-8, when I start /usr/local/bin/mysql, I cannot input Cyrillic (non-ascii) characters therein. If the database already contains Cyrillic data, I see them fine, just cannot type them at the prompt.

Of course I can input Cyrillic characters in my regular shell (tcsh), it's only the mysql shell that has this problem.

This is my MySQL environment:

root@gw:~ # mysql -e status
mysql  Ver 14.14 Distrib 5.6.38, for FreeBSD10.4 (amd64) using  EditLine wrapper

Connection id:		46
Current database:	
Current user:		root@localhost
SSL:			Not in use
Current pager:		stdout
Using outfile:		''
Using delimiter:	;
Server version:		5.6.38 Source distribution
Protocol version:	10
Connection:		Localhost via UNIX socket
Server characterset:	utf8
Db     characterset:	utf8
Client characterset:	utf8
Conn.  characterset:	utf8
UNIX socket:		/tmp/mysql.sock
Uptime:			1 day 15 hours 56 min 45 sec

Threads: 1  Questions: 464  Slow queries: 0  Opens: 88  Flush tables: 1  Open tables: 81  Queries per second avg: 0.003

 mysql> show create database bitrix;
| Database | Create Database                                                 |
| bitrix   | CREATE DATABASE `bitrix` /*!40100 DEFAULT CHARACTER SET utf8 */ |
1 row in set (0.00 sec)

Comment 1 Victor Sudakov 2017-11-06 06:49:19 UTC
I hear there was a recent switch from readline to EditLine, can it be the culprit? I don't remember having such a problem on previous versions of MySQL.

root@gw:~ # ldd /usr/local/bin/mysql
	libedit.so.0 => /usr/local/lib/libedit.so.0 (0x800a8a000)
	libz.so.6 => /lib/libz.so.6 (0x800cbe000)
	libm.so.5 => /lib/libm.so.5 (0x800ed5000)
	libexecinfo.so.1 => /usr/lib/libexecinfo.so.1 (0x8010fe000)
	libssl.so.7 => /usr/lib/libssl.so.7 (0x801301000)
	libcrypto.so.7 => /lib/libcrypto.so.7 (0x80156d000)
	libc++.so.1 => /usr/lib/libc++.so.1 (0x801965000)
	libcxxrt.so.1 => /lib/libcxxrt.so.1 (0x801c25000)
	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x801e42000)
	libthr.so.3 => /lib/libthr.so.3 (0x802050000)
	libc.so.7 => /lib/libc.so.7 (0x802274000)
	libncurses.so.8 => /lib/libncurses.so.8 (0x802623000)
	libelf.so.1 => /usr/lib/libelf.so.1 (0x802870000)
root@gw:~ #
Comment 2 Gleb Popov freebsd_committer 2020-04-25 14:10:52 UTC
It does work for me, with MySQL 5.7, at least. Maybe it was fixed meanwhile?