-
-
Notifications
You must be signed in to change notification settings - Fork 883
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
Remove redundant field CommentLike.post_id #4749
Conversation
@@ -59,7 +59,7 @@ impl VoteView { | |||
|
|||
comment_like::table | |||
.inner_join(person::table) | |||
.inner_join(post::table) | |||
.inner_join(comment::table.inner_join(post::table)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a difference in logic or performance if we put each of these individually on the top level chain? i.e.
comment_like::table
.inner_join(person::table)
.inner_join(comment::table)
.inner_join(post::table)
// etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There should be no difference because only 5 tables are joined, and the join collapse limit is set to 11, which means the database ignores the given join order
Lets mark as draft until |
I'll mark as ready to review, since we're merging breaking changes now. |
The migration for this one is dependent on #4459 , so luckily the CI will catch this until that one gets merged. |
Included in #5122 |
Required byrequires #4459