Skip to content
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

Open
macolo opened this issue Nov 26, 2019 · 3 comments

Comments

@macolo
Copy link

macolo commented Nov 26, 2019

Please see here https://stackoverflow.com/questions/54413800/why-does-the-deployment-process-return-below-error/59054898#59054898

@djjudas21
Copy link

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 😄

@djjudas21
Copy link

@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__'

@DmytroLitvinov
Copy link
Collaborator

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.

djjudas21 added a commit to camerahub/camerahub that referenced this issue Feb 13, 2020
djjudas21 added a commit to camerahub/camerahub that referenced this issue Feb 13, 2020
djjudas21 added a commit to camerahub/camerahub that referenced this issue Feb 13, 2020
djjudas21 added a commit to camerahub/camerahub that referenced this issue Feb 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants