Context Navigation

Changes between Initial Version and Version 9 of Ticket #17854

Timestamp:: Mar 13, 2012, 6:37:34 AM (13 years ago)
Author:: Ramiro Morales
Comment:: Would be acceptable to "fix" this by documenting the limitations of the three database engine/adaptors in the DB notes document?

Ticket #17854
- Property Component Uncategorized → Database layer (models, ORM)
- Property Summary DecimalField problem → Problem with DecimalField and big vlues of max_digits, decimal_places, sqlite3 backend
- Property Severity Release blocker → Normal
- Property Triage Stage Unreviewed → Accepted

-              initial
+              v9
+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)
+For a model field created as
+{{{
+models.DecimalField(max_digits = 200, decimal_places = 100, blank = False, null = False)
+}}}
+django version 1.3.1 and 1.4c1 (don't know about older versions);
+python 2.6.6;
+linux;
+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;