Bug #72108 | Hard to read history file | ||
---|---|---|---|
Submitted: | 24 Mar 2014 9:45 | Modified: | 24 Mar 2014 10:06 |
Reporter: | Valeriy Kravchuk | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Command-line Clients | Severity: | S3 (Non-critical) |
Version: | 5.6.16, 5.6.18, 5.7.5 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | client, editline, regression |
[24 Mar 2014 9:45]
Valeriy Kravchuk
[24 Mar 2014 10:06]
MySQL Verification Team
Hello Valeriy, Thank you for the bug report. Verified as described. Thanks, Umesh
[24 Mar 2014 10:08]
MySQL Verification Team
// 5.5 vs 5.6 // 5.5.38 # more ~/.mysql_history select version(); \q // 5.6.18 # more ~/.mysql_history _HiStOrY_V2_ select\040version(); \134q
[24 Mar 2014 10:11]
MySQL Verification Team
// 5.7.5 - affected # more ~/.mysql_history _HiStOrY_V2_ select\040version(); \134q
[31 Mar 2014 9:21]
Hartmut Holzgraefe
AFAIR this is a readline vs. libedit problem ...? Definitely not something new to 5.6, I remember having seen this every once in a while long before 5.6 was released ...
[9 Apr 2014 17:44]
Jonathan Nicol
related to http://bugs.mysql.com/bug.php?id=69991
[17 Aug 2014 12:29]
Daniƫl van Eeden
Also related: Bug #68925