-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Small optimization for getTeamIDs #919
Small optimization for getTeamIDs #919
Conversation
LGTM |
models/org.go
Outdated
@@ -563,18 +563,22 @@ func (org *User) getUserTeams(e Engine, userID int64, cols ...string) ([]*Team, | |||
Find(&teams) | |||
} | |||
|
|||
func (org *User) getOrgTeamIDs(e Engine, userID int64) ([]int64, error) { |
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.
Should this be getUserTeamIDs
(to match GetUserTeamIDs
)?
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.
done.
models/org.go
Outdated
Join("INNER", "team_user", "`team_user`.team_id = team.id"). | ||
Join("INNER", "user", "`user`.id=team_user.uid"). | ||
And("`team_user`.uid = ?", userID). | ||
Asc("`user`.name"). |
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.
Why is this ORDER BY
necessary? We are only looking for one user (i.e. the user with ID userID
)
Plus, if we get rid of the ORDER BY
, we won't need to join with the user
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.
done.
LGTM |
The latest XORM has supported only Find IDs. So let's use the new method.