#32676: Migration autodetector changes related_name for self-referential
ManyToManyField.
-------------------------------------+-------------------------------------
               Reporter:  Mariusz    |          Owner:  nobody
  Felisiak                           |
                   Type:  Bug        |         Status:  new
              Component:  Database   |        Version:  4.0
  layer (models, ORM)                |
               Severity:  Release    |       Keywords:
  blocker                            |
           Triage Stage:             |      Has patch:  0
  Unreviewed                         |
    Needs documentation:  0          |    Needs tests:  0
Patch needs improvement:  0          |  Easy pickings:  0
                  UI/UX:  0          |
-------------------------------------+-------------------------------------
 Migration autodetector no longer adds a model name to the `related_name`
 attribute for self-referential `ManyToManyField`, e.g. for a field
 {{{
 class MyModel2(models.Model):
     field_3 = models.ManyToManyField('self')
 }}}
 it creates a migration with `related_name='field_3_rel_+'` instead of
 `related_name='_mymodel2_field_3_+'`.

 Regression in aa4acc164d1247c0de515c959f7b09648b57dc42 (see #29899).

-- 
Ticket URL: <https://code.djangoproject.com/ticket/32676>
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.61c25767473adf0d004078615192498d%40djangoproject.com.

Reply via email to