[Tickets #11064] Re: Turba Browse is very inefficient

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/11064
------------------------------------------------------------------------------
  Ticket             | 11064
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Turba Browse is very inefficient
  Queue              | Turba
  Version            | Git master
  Type               | Enhancement
  State              | New
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2012-03-09 13:20) wrote:

>> Browsing in Turba (at least via SQL driver) will query ALL contacts
>> on every page, regardless if you are filtering - for example, by a
>> letter when using the alphabet pager.  It is the View code that is
>> doing the filtering.  This is incorrect behavior - the query should
>> be filtered at the DB level instead - it reduces overhead and SQL is
>> precisely designed for this kind of filtering, so it is the proper
>> tool for the job.
>
> Driver->search should support criteria like limit(n) and %like% or  
> startwith('a')
> This probably applies to more backends.

The problem, at least as I can tell, is that the way the Turba Views  
are designed.  The Browse View is passed a search result, and it is  
only in that view that the filter (from URL parameter data) is  
determined.

In other words, the filter can't be applied at the time the search is  
done based on the current architecture.