#33406: Micro-optimisation for Value._resolve_output_field (by modifying
CharField.__init__)
-------------------------------------+-------------------------------------
Reporter: Keryn Knight | Owner: Keryn
Type: | Knight
Cleanup/optimization | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
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
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"b894199eb08d9162e70f7115f91e1e9d2030fc9f" b894199]:
{{{
#!CommitTicketReference repository=""
revision="b894199eb08d9162e70f7115f91e1e9d2030fc9f"
Refs #33406 -- Added test for not creating broken validators when
resolving Value.output_field.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33406#comment:5>
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.97eae911af67a3056990af23ac5a801b%40djangoproject.com.
