Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
1.0.15, 1.1.6, 1.2.2
-
None
Description
After loading data (using cpimport), noticed some issues with it. When I load the data using cpimport, the field value which is stored as in scientific form (8e-05), it gets loaded into the database as 0.000008 instead of 0.000080
When I use the regular load infile command, the data is loaded just fine.
[root@localhost ~]# cat t1.dat
|
8e-5|8e-5|8e-5|
|
after cpimport, I got
|
MariaDB [mytest]> select * from t1;
|
+------------+---------+---------+
|
| c1 | c2 | c3 |
|
+------------+---------+---------+
|
| 0.00000008 | 0.00008 | 0.00008 |
|
+------------+---------+---------+
|
1 row in set (0.155 sec)
|
so issue is with cpimport on decimal column
|
insert looks good
|
MariaDB [mytest]> insert t1 values (8e-5,8e-5,8e-5);
|
Query OK, 1 row affected (0.439 sec)
|
 |
MariaDB [mytest]> select * from t1;
|
+------------+---------+---------+
|
| c1 | c2 | c3 |
|
+------------+---------+---------+
|
| 0.00000008 | 0.00008 | 0.00008 |
|
| 0.00008000 | 0.00008 | 0.00008 |
|
+------------+---------+---------+
|
2 rows in set (0.194 sec)
|
first row is cpimport, 2nd row is insert. Insert matched that on Innodb
|
Attachments
Issue Links
- causes
-
MCOL-2149 Regression in decimal saturation handling in cpimport
- Closed