#23801: IntegerField w/ max_length silently truncates integers
-------------------------------------+-------------------------------------
Reporter: eykd | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I am not sure how to proceed given in #22637 "the opinion was that the
`max_length` option should not be forbidden in order to keep Django upward
compatible, but that it also does not make sense for the `IntegerField`. I
suppose we could add a warning using the checks framework (which could be
silenced by those intentionally using `max_length` on `IntegerField` for
some reason). Do you have any suggestions?
--
Ticket URL: <https://code.djangoproject.com/ticket/23801#comment:1>
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/062.cdc6f319b891278f03a74669ac53351f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
