Opened 13 years ago
Last modified 9 years ago
#17854 new New feature
DecimalField problem — at Initial Version
Reported by: | anonymous | Owned by: | nobody |
---|---|---|---|
Component: | Core (System checks) | Version: | dev |
Severity: | Normal | Keywords: | DecimalField bug |
Cc: | Walter Doekes | Triage Stage: | Accepted |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
For a model field created as :: models.DecimalField(max_digits = 200, decimal_places = 100, blank = False, null = False)
While using admin interface to insert a record involving such a DecimalField, the format changes (loss of precision and it uses scientific notation (even in the database)) (Please note - it works properly for low precision values (example - .987654321001234) - but for larger precision values (probably 15 decimal_places or more) it results in loss of precision)
django version 1.3.1 and 1.4c1 (don't know about older versions);
python 2.6.6;
linux;