#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 timo):
As discussed with Shai on IRC, column names are auto-truncated in Oracle
so the model check isn't needed so much there, or at least the errors
should be reduced to warnings. 3rd-party backends may implemented similar
behavior so we should keep that in mind when deciding on a solution.
--
Ticket URL: <https://code.djangoproject.com/ticket/13711#comment:19>
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.22581259a8c58ae65a614acb567997b9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
