Patch #21611
closed
Do not collect ids of subtree in Query#project_statement
Added by Ondřej Ezr almost 9 years ago.
Updated almost 9 years ago.
Category:
Code cleanup/refactoring
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
- Target version set to Candidate for next major release
- Related to Defect #19976: Redmine can't work with 3000 projects added
- Related to Feature #19102: Redmine doesnt scale with large amount of projects added
The patch breaks a few tests. It displays issues from subpprojects even if display_subprojects_issues setting is disabled.
I see... I frogot one case in the statement.
Thanks for updating the patch. It have passed all tests.
- Target version changed from Candidate for next major release to 3.3.0
- 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
Also available in: Atom
PDF