#24818: models.CharField shouldn't accept a string as max_length
-------------------------------------+-------------------------------------
Reporter: slamora | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by slamora):
Replying to [comment:5 bmispelon]:
> Is there a reason why we can't cast `max_length` to an integer value in
`Field.__init__`?
Because that will mask the real "problem" as has happened with the current
implementation that casts {{{ mask_length }}} at {{{
_check_max_length_attribute }}}.
IMHO, Django shouldn't handle user's fault but warn the user about it.
--
Ticket URL: <https://code.djangoproject.com/ticket/24818#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.1256d433b814f5223a12fb4eb917990b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
