[MDEV-15263] Different justification behaviour for integer mysql client output Created: 2018-02-09  Updated: 2020-08-25  Resolved: 2018-06-14

Status: Closed
Project: MariaDB Server
Component/s: libmariadb
Affects Version/s: 10.1, 10.2
Fix Version/s: 10.2.16, 10.3.8

Type: Bug Priority: Minor
Reporter: Richard Stracke Assignee: Georg Richter
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MDEV-15459 Window Functions seems to return stri... Closed

 Description   

Justification is different between Columnstore

To reproduce:

connect with mysql client.

 
Columnstore 1.1
 
 MariaDB [(none)]> select 'blub',sum(3454435+43244);
 +------+--------------------+
 | blub | sum(3454435+43244) |
 +------+--------------------+
 | blub | 3497679            |
 

 MariaDB 10.1
 
 MariaDB [mysql]>  select 'blub',sum(3454435+43244);
 +------+--------------------+
 | blub | sum(3454435+43244) |
 +------+--------------------+
 | blub |            3497679 |
 +------+--------------------+



 Comments   
Comment by Elena Stepanova [ 2018-02-09 ]

Something has changed on the client side between 10.2.1 and 10.2.2:

$ /data/releases/10.2.2/bin/mysql -uroot --protocol=tcp -e "select 'blub',sum(3454435+43244);"
+------+--------------------+
| blub | sum(3454435+43244) |
+------+--------------------+
| blub | 3497679            |
+------+--------------------+
$ /data/releases/10.2.1/bin/mysql -uroot --protocol=tcp -e "select 'blub',sum(3454435+43244);"
+------+--------------------+
| blub | sum(3454435+43244) |
+------+--------------------+
| blub |            3497679 |
+------+--------------------+

Comment by Georg Richter [ 2018-02-19 ]

It will be pushed after merge of diverged branches is finished.

The IS_NUM macro was never updated (MariaDB Connector/C was built on top of LGPL MySQL 3.23.58 client library).

Additional todo's:

  • Prefixing all macro's with MARIADB_ prefix (for backwards compatibiliry we will still support the IS_ macros
  • Adding documentation for definitions
Generated at Thu Feb 08 08:19:56 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.