search

mypebble / django-pgviews

Fork of django-postgres that focuses on maintaining and improving support for Postgres SQL Views.
The Unlicense
195 stars 41 forks source link

AppRegistryNotReady raises #36

Open arsen-movsesyan opened 6 years ago

arsen-movsesyan commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

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?