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

Feature request: Handle Django deferred fields #39

Open
shaib opened this issue Jun 16, 2021 · 0 comments · May be fixed by #41
Open

Feature request: Handle Django deferred fields #39

shaib opened this issue Jun 16, 2021 · 0 comments · May be fixed by #41

Comments

@shaib
Copy link

shaib commented Jun 16, 2021

This library is very helpful in the classic 1+n scenario, where the n queries are caused by following relationships.

There is another, less common scenario, with similar consequences: The original query defers some field, and then the field is accessed when going over the objects. It may seem very unlikely, because deferring has to be done explicitly, but can still happen when the deferring and the access are done in different parts of the code, and much like the classic case, can be improved by adding a call (e.g. defer(None)).

@shaib shaib linked a pull request Jun 16, 2021 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant