#29598: contrib.postgres.FloatRangeField should be renamed DecimalRangeField
--------------------------------------------+------------------------
Reporter: Simon Charette | Owner: (none)
Type: Bug | Status: new
Component: contrib.postgres | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
--------------------------------------------+------------------------
As discovered in https://code.djangoproject.com/ticket/25591#comment:6
`FloatRangeField` uses `numrange` as database type which is not
appropriate to store doubles/floats which is what `FloatField` uses.
`DecimalField` on the other hand uses `numeric` as datatype which makes a
better abstraction resolution. I suggest we keep `class
FloatRangeField(DecimalRangeField)` field around with warning on
`__init__` during the deprecation period.
--
Ticket URL: <https://code.djangoproject.com/ticket/29598>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.b9e3789a51d82c22f277960a05e62628%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
