#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: Normal | Resolution: fixed Keywords: | Triage Stage: Ready for Has patch: 1 | checkin Needs tests: 0 | Needs documentation: 0 Easy pickings: 0 | Patch needs improvement: 0 | UI/UX: 0 -------------------------------------+------------------------------------- Changes (by Tim Graham <timograham@…>):
* status: assigned => closed * resolution: => fixed Comment: In [changeset:"91f1b6dcdc5da47d7794a55e3114820407a5bd62"]: {{{ #!CommitTicketReference repository="" revision="91f1b6dcdc5da47d7794a55e3114820407a5bd62" Fixed #13711 -- Model check added to ensure that auto-generated column name is within limits of the database. Thanks russellm for report and Tim Graham for review. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/13711#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 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.8da9d4dbbf380dd0780a7d1ea9461ae5%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.