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

AppRegistryNotReady raises #36

Open
arsen-movsesyan opened this issue Mar 4, 2018 · 2 comments
Open

AppRegistryNotReady raises #36

arsen-movsesyan opened this issue Mar 4, 2018 · 2 comments

Comments

@arsen-movsesyan
Copy link

The scenario is out of the box. When model is get created it cannot release projections and raises AppRegistryNotReady.

(see django-pgviews/view.py line 214)

Maybe I missed something on how to defer loading until registry is get populated...

For this particular project I use Django ver. 2.0
Based on documentation it is not supported, but I'd be glad to contribute myself. Just need some input on direction to go.

Thank you

@kennydude
Copy link
Contributor

I haven't tested this on Django 2.0 neither, so if you can figure it out feel free to send in a PR :)

@scott-w
Copy link
Contributor

scott-w commented Jul 25, 2018

Hey @arsen-movsesyan just to update you. I updated a few applications to Django 2.0 back in February and I don’t think I saw the issue you mentioned. At least I don’t recall doing anything special to work around it. Are you using the inferred projections as opposed to passing raw SQL?

@tpict You’re closer to the codebase than me now. Just checking the above is correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants