#32967: Buggy Migrations when `float("nan")` in `Q` objects
-------------------------------------+-------------------------------------
Reporter: Steven Jin | Owner: Steven
| Jin
Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: db Q | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: assigned => closed
* resolution: => wontfix
Comment:
Thanks for the report, however it looks like a hypothetical issue, what do
you want to check with such constraint? (`float('nan') != whatever)`.
`FloatField` uses a proper data type and this should be ensured on a
database layer without extra constraints. I don't think it's worth
additional complexity.
--
Ticket URL: <https://code.djangoproject.com/ticket/32967#comment:6>
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/068.88e1253765ccf17eb31acbb49e629405%40djangoproject.com.
