#36673: DecimalField max_digits and decimal_places should be optional and more
general
-------------------------------------+-------------------------------------
Reporter: Gavin Wahl | Owner: (none)
Type: New feature | Status: closed
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Gavin Wahl):
That ticket requests an "ImpreciseDecimalField" to represent floating-
point (approximate) fields. Django's DecimalField is used to represent
exact values.
The Oracle inspectdb bug from the mailing list and ticket look like a
floating-point Oracle field getting incorrectly introspected as a
DecimalField instead of FloatField (perhaps this was before FloatField
existed?). I can contribute a patch to fix the DecimalField validation; I
can't fix Oracle introspection.
--
Ticket URL: <https://code.djangoproject.com/ticket/36673#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019a03d5016b-6e07f208-d081-430b-a455-aaf652280914-000000%40eu-central-1.amazonses.com.
