Actions
Patch #43214
closed
Optimize Project.allowed_to_condition by replacing `projects.status <> ...` with `projects.status IN (...)`
Description
The attached patch replaces the condition projects.status <> ... with the equivalent projects.status IN (...) in the Project.allowed_to_condition method.
This change makes the SQL clearer and may improve performance, since IN (...) is generally more optimizer-friendly than a combination of <> conditions. A performance benefit of this approach was also observed during the investigation of #40728 (see #40728#note-15 and #40728#note-16).
Files
Related issues
Updated by Go MAEDA about 2 months ago
- Subject changed from Optimize Project.allowed_to_condition by `replacing projects.status <> ...` with `projects.status IN (...)` to Optimize Project.allowed_to_condition by replacing `projects.status <> ...` with `projects.status IN (...)`
Updated by
Updated by Go MAEDA about 2 months ago
- Description updated (diff)
- Target version set to 6.1.0
Updated by Go MAEDA about 2 months ago
- Related to Feature #36691: Background job and dedicated status for project deletion added
Updated by Go MAEDA about 2 months ago
- Status changed from New to Closed
- Assignee set to Go MAEDA
Thank you for reviwing the change. I have committed the change in r23979.
Actions