Bug #24558 Increasing decimal column length causes data loss

Description:
I have a DECIMAL(18) column with an 18-digit number in it.
I alter the table so that the column is DECIMAL(19).
There is a warning and the number is changed.

See also bug#18014 (closed).

How to repeat:
mysql> create table t77 (s1 decimal(18)) engine=myisam;
Query OK, 0 rows affected (0.01 sec)

mysql> insert into t77 values (123456789012345678);
Query OK, 1 row affected (0.01 sec)

mysql> alter table t77 modify column s1 decimal(19);
Query OK, 1 row affected, 1 warning (0.01 sec)
Records: 1  Duplicates: 0  Warnings: 1

mysql> show warnings;
+-------+------+-----------------------------------------+
| Level | Code | Message                                 |
+-------+------+-----------------------------------------+
| Note  | 1265 | Data truncated for column 's1' at row 1 |
+-------+------+-----------------------------------------+
1 row in set (0.00 sec)

mysql> select * from t77;
+--------------------+
| s1                 |
+--------------------+
| 123456789012345700 |
+--------------------+
1 row in set (0.00 sec)

Thank you for the bug report. Verified as described on Suse 10 32-bit.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/17835

ChangeSet@1.2354, 2007-01-10 13:38:00+04:00, ramil@mysql.com +3 -0
  Fix for bug #24558: Increasing decimal column length causes data loss
  
  Altering to a decimal field we get double value then store it 
  that may cause data loss. 
  Fix: use store_decimal() instead.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/21976

ChangeSet@1.2466, 2007-03-15 12:06:06+04:00, ramil@mysql.com +3 -0
  Fix for bug #24558: Increasing decimal column length causes data loss
  
  Altering to a decimal field we get double value then store it 
  that may cause data loss. 
  Fix: use store_decimal() instead.

Fixed in 5.0.40 and 5.1.17

Noted in 5.0.40, 5.1.17 changelogs.