#22305: MaxLengthValidator doesn't take database encoding into account
--------------------------------------+------------------------------------
Reporter: joeri | Owner: nobody
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version: master
Severity: Normal | Resolution: fixed
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 Tim Graham <timograham@…>):
In [changeset:"1c714c18d22a38ad2dca696ca8bc4201cc3da131"]:
{{{
#!CommitTicketReference repository=""
revision="1c714c18d22a38ad2dca696ca8bc4201cc3da131"
[1.6.x] Fixed #22305 -- Added note to docs about UTF8 database
requirement.
Backport of 08b85de9b7 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/22305#comment:7>
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/063.7095b5d419db3335fc55f2f00f1cd5a5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
