[Django] #26114: Removing Meta.db_table generates migration with wrong rename (None)

[Django]

#26114: Removing Meta.db_table generates migration with wrong rename (None)
----------------------------+--------------------
     Reporter:  dvinegla    |      Owner:  nobody
         Type:  Bug         |     Status:  new
    Component:  Migrations  |    Version:  1.9
     Severity:  Normal      |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0           |      UI/UX:  0
----------------------------+--------------------
 {{{
 # myapp.models.py

 #Old model
 class MyModel(models.Model):
     ...
     class Meta:
         db_table = 'legacy_table'

 #New model
 class MyModel(models.Model):
     ...

 # makemigrations output:
 - Rename table for mymodel to None

 # sqlmigrate output:
 BEGIN;
 --
 -- Rename table for mymodel to None
 --
 RENAME TABLE `legacy_table` TO `myapp_mymodel`;

 COMMIT;

 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/26114>
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/051.dba3357d1df0c36180bc29caf36b8829%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.