#22637: Documentation not clear about the effects of max_length for IntegerField
-------------------------------+-----------------------------------------
Reporter: msn@… | Owner: sabinemaennel
Type: Bug | Status: assigned
Component: Documentation | Version: 1.7-beta-2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------+-----------------------------------------
Comment (by sabinemaennel):
Hello ,
I just tested this. This is my result:
Assigning the option `max_length` to an `IntegerField` in your model does
not have any effect, neither on the database where the field is just
generated as an `models.IntegerField()` nor on the Admin Form, where the
field is always generated as `"type=text"`and `class="vIntegerField"`. So
it does not really make sense to have that option here.
I talked about this with chai about this and the opinion was that the
option should not be forbidden in order to keep Django upward compatible,
but that it also does not make sense for the `IntegerField`.
--
Ticket URL: <https://code.djangoproject.com/ticket/22637#comment:3>
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/077.bce0b49e078ae8a9b3a1fbe7e0b77a0d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
