Fix for critical DB error with postgres backend #232
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
|
Could subquery be used instead to keep the same eager loading semantics? |
|
@ivar-lazzaro : Thanks for this suggestion. "subquery" also seems to work fine in this case. |
|
@ivar-lazzaro : Do you have any other suggestion. Can we merge this ? |
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.
Fixes: #231
The commit updates the tree_model in migration to use lazy_load (http://docs.sqlalchemy.org/en/latest/orm/loading_relationships.html#lazy-loading) which emits a SELECT statement instead of the Joined Eager Loading (http://docs.sqlalchemy.org/en/latest/orm/loading_relationships.html#joined-eager-loading ) which emits a LEFT OUTER JOIN by default on the SELECT statement causing the postgres backend to produce the error.