[MDEV-10073] Abnormal behavior of mariadb client after pressing some up and down key Created: 2016-05-16  Updated: 2017-06-26  Resolved: 2017-06-26

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

Type: Bug Priority: Minor
Reporter: sachin setiya (Inactive) Assignee: Sergei Golubchik
Resolution: Cannot Reproduce Votes: 0
Labels: client
Environment:

Arch linux 4.5.0-1 , deepin terminal ,gnome terminal ,x64



 Description   

When you are using mariadb client for long time you will find that after pressing up key
something like this happens

MariaDB [backup1]> MariaDB [backup1abc);
 
MariaDB [employees]> MariaDBdistinct salary[employees]> select * from salaries;
 
MariaDB [unique_index]> create table a1 (xyz blob , abc char(20) as(left(xyz,20)) persistent );MariaDB [unique_index]> create table a1 (xyz blob , abc as(left(xyz,20)) persist

it is like previous query and maridb[db_name] show up in current query. it happens quite rarely.



 Comments   
Comment by Elena Stepanova [ 2016-05-27 ]

I guess it might be the terminal problem as well as anything else, it's going to be hard to figure out if there is no way to reproduce it more or less reliably.
serg, What do you think?

Comment by Sergei Golubchik [ 2016-05-31 ]

Yes. sachin007 what are your TERM, LANG, and LC_* environment variables? And your mysql command client prompt value?

Comment by sachin setiya (Inactive) [ 2016-05-31 ]

Term = tried on terminator,gnome terminal,deepin terminal
Lang = english
LC_* all default i did not set anything

Comment by Sergei Golubchik [ 2016-05-31 ]

What's the output of

env|grep '\(LANG\|LC_\|TERM\)'

Comment by sachin setiya (Inactive) [ 2016-05-31 ]

for gnome terminal

LANG=en_US.UTF-8
COLORTERM=truecolor
GDM_LANG=en_US.UTF-8
TERM=xterm-256color
LC_CTYPE=en_US.UTF-8

for terminator

LANG=en_US.UTF-8
COLORTERM=gnome-terminal
TERMINATOR_UUID=urn:uuid:12e3e77d-851b-45cc-9d99-9aef0efed9f8
GDM_LANG=en_US.UTF-8
TERM=xterm
LC_CTYPE=en_US.UTF-8

Generated at Thu Feb 08 07:39:28 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.