#13711: Very long field names on models cause problems
-------------------------------------+-------------------------------------
Reporter: russellm | Owner:
Type: Bug | anubhav9042
Component: Database layer | Status: closed
(models, ORM) | Version: master
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by anubhav9042):
I have made a patch for what I suggested:
https://github.com/coder9042/django/compare/gsoc_13711
IMO this is the right way for this issue and also now the check runs for
all backends rather than only for the one with minimum allowed length.
Also the backends with the `connection.feature.supports_auto_truncation`
set to `True` are skipped.
--
Ticket URL: <https://code.djangoproject.com/ticket/13711#comment:22>
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/066.d80075f1c873d9233b003c2f74881504%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
