-
Notifications
You must be signed in to change notification settings - Fork 90
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
relation "django_content_type" does not exist when migrating the db from scratch #183
Comments
I am running into this issue too. I understand the workaround but I have ~30 forms to add this to 😢 Is there a fix in the pipeline? Thanks 😄 |
@macolo most of my forms are defined without explicitly naming the fields. Do I need to define each field explicitly so I can benefit from your workaround? class AccessoryForm(ModelForm):
class Meta:
model = Accessory
fields = '__all__' |
Hi @djjudas21 , Sometimes it is not necessary to define all of fields for specific form. So as a workaround it should be fixed as it is described in the link. |
Please see here https://stackoverflow.com/questions/54413800/why-does-the-deployment-process-return-below-error/59054898#59054898
The text was updated successfully, but these errors were encountered: