#33954: "NaN" can be stored in DecimalField but cannot be retrieved
-------------------------------------+-------------------------------------
Reporter: Xabier Bello | Owner: Mohamed
Type: | Karam
Cleanup/optimization | Status: closed
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"b92ffebb0cdc469baaf1b8f0e72dddb069eb2fb4" b92ffebb]:
{{{
#!CommitTicketReference repository=""
revision="b92ffebb0cdc469baaf1b8f0e72dddb069eb2fb4"
Fixed #33954 -- Prevented models.DecimalField from accepting NaN, Inf, and
-Inf values.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33954#comment:8>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/01070182dfb06cb2-354ac844-c912-4ca8-abb0-0b1caf66f5ee-000000%40eu-central-1.amazonses.com.
