extern/egroupware
1
0
Fork 1
mirror of https://github.com/EGroupware/egroupware.git synced 2024-11-16 13:03:12 +01:00
Code Issues Packages Projects Releases Wiki Activity

disabling dates_range_view in favor of using dates-table direct, as it appears 1.5-3 times quicker in two big installations I tested with

Browse Source
This commit is contained in:
Ralf Becker 2015-02-18 08:16:16 +00:00
parent ec03148f1a
commit 843bbd1dc1
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
calendar/inc/class.calendar_so.inc.php
View File

@ -161,6 +161,9 @@ class calendar_so
/** /**
* Return sql to fetch all dates in a given timerange, to be used instead of full dates table in further sql queries * Return sql to fetch all dates in a given timerange, to be used instead of full dates table in further sql queries
* *
* Currently NOT used, as using two views joined together appears slower in my tests (probably because no index) then
* joining cal_range_view with real dates table (with index).
*
* @param int $start * @param int $start
* @param int $end * @param int $end
* @param array $_where =null * @param array $_where =null
@ -848,7 +851,8 @@ class calendar_so
// dates table join only needed to enum recuring events, we use a time-range limited view here too // dates table join only needed to enum recuring events, we use a time-range limited view here too
if ($params['enum_recuring']) if ($params['enum_recuring'])
{ {
$join = "JOIN ".$this->dates_range_view($start, $end, null, $filter == 'everything' ? null : $filter == 'deleted'). $join = "JOIN ".$this->dates_table. // using dates_table direct seems quicker then an other view
//$this->dates_range_view($start, $end, null, $filter == 'everything' ? null : $filter == 'deleted').
" ON $this->cal_table.cal_id=$this->dates_table.cal_id ".$join; " ON $this->cal_table.cal_id=$this->dates_table.cal_id ".$join;
} }