refactor: drop django-tree-queries & implement array-based tree functions #478
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ions The Django-Tree-Queries, together with some visibility queries, causes a ton of heavy performance problems. Therefore, we now implement the tree functionality for Scopes by using an array field to "cache" all the parent PKs of every scope. This allows us to write some much more efficient queries that don't rely on CTEs, and enables subqueries where we previously had to explode a QS to perform the same functionality.
winged
force-pushed
the
fully_self_implemented_hierarchical_queries
branch
from
66c7afa
to
30ed6c4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Django-Tree-Queries, together with some visibility queries, causes a ton of heavy performance problems. Therefore, we now implement the tree functionality for Scopes by using an array field to "cache" all the parent PKs of every scope.
This allows us to write some much more efficient queries that don't rely on CTEs, and enables subqueries where we previously had to explode a QS to perform the same functionality.