Description:
When removing a decimal field from a content type (which already exists in another content type), values after the decimal point are truncated.

Steps to Reproduce:
Create a new content type (CT1) and add a new decimal field (FIELD1).
Create a new instance of CT1 (TEST1) and add value in FIELD1 = 45.1234567
Create a new content type (CT2) and add field FIELD1.
Checking TEST1, FIELD1 = 45.1235
Edit content type CT2 and remove FIELD1.
Checking TEST1, FIELD1 = 45
!!!!

Notes:
This happened to me on a live site (luckily I had a backup), and I ran a test to reproduce it and got the same result. When using the same field for two content types, CCK creates a new table for the field and adds all instances of that field to the table. If the field is removed from a content type, the field is put back into the content types table, and it is obviously during this process that the decimal values get truncated.

Ran this with Drupal6 (6.x-2.0-RC6) and there does not appear to be this issue, so perhaps this has already been reported and only fixed in cck 2.0.

Comments

karens’s picture

Status: Active » Closed (won't fix)

This is a limitation of the float field used in D5. See #501016: Big numbers (>10,000) get rounded up and other reports. This won't get fixed in D5. D6 has a proper decimal field.