#2495: db.models.TextField cannot be marked unique when using mysql backend
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner:
| Honza_Kral
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: mysql TextField | 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:"4f83bfa9e5ef10c6c9711ad529630d09a06ef413" 4f83bfa]:
{{{
#!CommitTicketReference repository=""
revision="4f83bfa9e5ef10c6c9711ad529630d09a06ef413"
[1.8.x] Refs #2495 -- Documented that MySQL cannot have
TextField(unique=True).
Backport of e8cbc2b322d873a6fe39faca18d340ce93035087 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/2495#comment:17>
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/067.2df5871a589feec523f91b2baf4967cd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
