-
Notifications
You must be signed in to change notification settings - Fork 67
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
Refactor Django model class names #837
Comments
Or I wonder if we could just manually rename the columns in PostgresSQL after changing the model names... |
Looks like Django 2 helps you refactor/rename model names https://stackoverflow.com/a/26241640
|
OK, I just did this on my local system and it was painless. I think I'll have to get Jason involved, however, as it requires running migration commands.
|
This has now been addressed and changes pushed to both -test and production |
When we originally wrote some models like
Project_header
andProject_umbrella
, we didn't follow best naming practices. And it's bothered me ever since. These should beProjectHeader
andProjectUmbrella
respectively.However, it's not a matter of simply renaming these in code because they are actually table names in PostgreSQL. So, we have to write custom migration code to handle this. Shouldn't be too difficult but will require some work.
The text was updated successfully, but these errors were encountered: