| Summary | huge amount of queries |
| Queue | Kronolith |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | |
| Requester | dgehl (at) inverse (dot) ca |
| Created | 08/31/2006 (6857 days ago) |
| Due | |
| Updated | 08/31/2006 (6857 days ago) |
| Assigned | |
| Resolved | 08/31/2006 (6857 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
even more into a single $addLinks variable in both HEAD and
FRAMEWORK_3. Thank you!
Kronolith::hasPermission('max_events') is called for every day of the
month view.
When I move the function call outside the 'foreach day' loop, the
number of database queries drops dramatically.
Here's a diff
RCS file: /repository/kronolith/lib/Views/Month.php,v
retrieving revision 1.9
diff -r1.9 Month.php
122c122
<
---
<
162,163c161,162
< Kronolith::hasPermission('max_events') === true ||
< Kronolith::hasPermission('max_events') >
Kronolith::countEvents())) {
---
$hasPermission > Kronolith::countEvents())) {
State ⇒ Not A Bug
specifically. This is not useful to us as a bug report or enhancement.
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ huge amount of queries
Queue ⇒ Kronolith
New Attachment: kronolith.log
State ⇒ Unconfirmed
enormous amount of SQL queries (even with
$conf['group']['cache'] = true;
$conf['share']['cache'] = true;
)