#33406: Micro-optimisation for Value._resolve_output_field (by modifying
CharField.__init__)
-------------------------------------+-------------------------------------
Reporter: Keryn Knight | Owner: Keryn
Type: | Knight
Cleanup/optimization | Status: closed
Component: Database layer | Version: dev
(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:"0ed2919814c80e31626dffdb6b80d0c20d43452f" 0ed29198]:
{{{
#!CommitTicketReference repository=""
revision="0ed2919814c80e31626dffdb6b80d0c20d43452f"
Fixed #33406 -- Avoided creation of MaxLengthValidator(None) when
resolving Value.output_field for strings.
This brings the behaviour in line with Field subclasses which append to
the validators within __init__(), like BinaryField, and prevents the
creation of a validator which incorrectly throws a TypeError, if it
were used.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33406#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/067.a72a39cba42efbbbaf2c70e09c533123%40djangoproject.com.
