| Bug #24558 | Increasing decimal column length causes data loss | ||
|---|---|---|---|
| Submitted: | 23 Nov 2006 20:35 | Modified: | 30 Mar 2007 19:30 | 
| Reporter: | Peter Gulutzan | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Data Types | Severity: | S3 (Non-critical) | 
| Version: | 5.1.14-beta-debug/5.0BK | OS: | Linux (SUSE 10.0 / 64-bit) | 
| Assigned to: | Ramil Kalimullin | CPU Architecture: | Any | 
   [23 Nov 2006 20:35]
   Peter Gulutzan        
  
 
   [23 Nov 2006 23:24]
   MySQL Verification Team        
  Thank you for the bug report. Verified as described on Suse 10 32-bit.
   [10 Jan 2007 9:38]
   Bugs System        
  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.
   [15 Mar 2007 8:06]
   Bugs System        
  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.
   [22 Mar 2007 20:01]
   Mads Martin Joergensen        
  Fixed in 5.0.40 and 5.1.17
   [30 Mar 2007 19:30]
   Paul DuBois        
  Noted in 5.0.40, 5.1.17 changelogs.

