#33119: Change casing of a model's name referenced by ManyToManyField generates
unnecessary migrations.
-------------------------------------+-------------------------------------
     Reporter:  AliGhotbizadeh       |                    Owner:  nobody
         Type:  Bug                  |                   Status:  closed
    Component:  Migrations           |                  Version:  3.2
     Severity:  Normal               |               Resolution:  fixed
     Keywords:                       |             Triage Stage:
  M2M,RenameModel,deconstruct        |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Mariusz Felisiak <felisiak.mariusz@…>):

 In [changeset:"b8f3a3ad54b05b83774716483afac7d0b9535fb4" b8f3a3a]:
 {{{
 #!CommitTicketReference repository=""
 revision="b8f3a3ad54b05b83774716483afac7d0b9535fb4"
 Refs #33119 -- Added tests for changing model name case referenced by
 ManyToManyField.

 Fixed in aa4acc164d1247c0de515c959f7b09648b57dc42.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33119#comment:2>
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.3940f98dfb090a0b5e0fe2dbd9ea3b28%40djangoproject.com.

Reply via email to