-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
This commit will reduce join star, repo_topic, topic tables on repo search, so that fix extra columns problem on mssql #5136
This commit will reduce join star, repo_topic, topic tables on repo search, so that fix extra columns problem on mssql #5136
Conversation
Tests seem to fail |
…earch, so that fix extra columns problem on mssql
bd17058
to
0d2dd17
Compare
@lafriks The previous test assertion is wrong. See https://github.com/go-gitea/gitea/blob/master/models/fixtures/repo_topic.yml, there is three records and 2 repos which topic name is graphql (id:4) and golang(id:1). So correct results should repo [1, 33], count 2, not [1, 33, 33] count 3. @appleboy |
Codecov Report
@@ Coverage Diff @@
## master #5136 +/- ##
==========================================
- Coverage 37.47% 37.47% -0.01%
==========================================
Files 310 310
Lines 45935 45921 -14
==========================================
- Hits 17216 17209 -7
+ Misses 26242 26237 -5
+ Partials 2477 2475 -2
Continue to review full report at Codecov.
|
@lunny please send backport to release/1.6 |
…earch, so that fix extra columns problem on mssql (go-gitea#5136) * This commit will reduce join star, repo_topic, topic tables on repo search, so that fix extra columns problem on mssql * fix tests
This commit removed join star, repo_topic, topic tables on repo search, so that fix extra columns problem on mssql database. Also, it maybe results in some performance reduce since it used some sub query instead join query.
This will partilly fix #4282.