mirror of
https://github.com/EGroupware/egroupware.git
synced 2024-11-23 00:13:35 +01:00
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
This commit is contained in:
parent
5bb6635822
commit
3a06bcb285
@ -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;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user