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.

Sign up for GitHub

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

Jump to bottom

Make sure the ContentType table exists before querying it in ContentTypeReference.__call__ #38

Open
charettes opened this issue Dec 17, 2016 · 1 comment
Open

Make sure the ContentType table exists before querying it in ContentTypeReference.__call__ #38

charettes opened this issue Dec 17, 2016 · 1 comment

Comments

@charettes
Copy link
Owner

charettes commented Dec 17, 2016 •
edited

This is a workaround for Django #24182.
@charettes charettes mentioned this issue Dec 17, 2016
Closed
@charettes
Copy link
Owner Author

Two things to do here:

  • If the django_contenttype table is missing we should return None. It should be safe as no relations could be pointing to the table yet anyway.
  • If the latest contenttypes migration is not applied we should fallback to manual querying,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@charettes