-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unchanged db_table
in RenameModel
raises Unsafe.ALTER_TABLE_RENAME
#26
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Renaming a model with a fixed table name (e.g.
Book
toOldBook
) will lead to a migration that raisesALTER_TABLE_RENAME
, when no schema changes occur.To Reproduce
Django model with
Meta.db_table = 'table_name'
hard codedRenaming the class from
Book
toOldBook
will lead to a migration that raisesALTER_TABLE_RENAME
, when in actuality no schema changes occur. (Correct me if I'm mistaken!)Expected behavior
When database tables are unaltered, don't raise
Versions:
The text was updated successfully, but these errors were encountered: