Actions
Patch #21611
closedDo not collect ids of subtree in Query#project_statement
Status:
Closed
Priority:
Normal
Assignee:
Category:
Code cleanup/refactoring
Target version:
Start date:
Due date:
% Done:
0%
Estimated time:
Description
It is inefficient in larger subtree - it would be nicer with pluck, but it would still result in ugly queries with more projects.
Best way is to use subquery in that cases
Files
Related issues
Updated by Go MAEDA almost 9 years ago
- Target version set to Candidate for next major release
According to #21608#note-3, this patch will resolve #19976 and #19102.
Updated by Go MAEDA almost 9 years ago
- Related to Defect #19976: Redmine can't work with 3000 projects added
Updated by Go MAEDA almost 9 years ago
- Related to Feature #19102: Redmine doesnt scale with large amount of projects added
Updated by Jean-Philippe Lang almost 9 years ago
The patch breaks a few tests. It displays issues from subpprojects even if display_subprojects_issues setting is disabled.
Updated by Ondřej Ezr almost 9 years ago
I see... I frogot one case in the statement.
Updated by Go MAEDA almost 9 years ago
Thanks for updating the patch. It have passed all tests.
Updated by Toshi MARUYAMA almost 9 years ago
- Target version changed from Candidate for next major release to 3.3.0
Updated by Jean-Philippe Lang almost 9 years ago
- Subject changed from Query project_statement - do not collect ids of subtree. to Do not collect ids of subtree in Query#project_statement
- Category set to Code cleanup/refactoring
- Status changed from New to Closed
- Assignee set to Jean-Philippe Lang
Committed, thanks!
Actions