Tickets :: Comment on [#11064] Turba Browse is very inefficient

* Your Email Address
* Spam protection	Enter the letters below: .__.. ..__ .__..__ \| \|\ /[ __\| \|[__) \|__\| \/ [_./\|__\\| \
Comment	>>> 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.
Attachment
Watch this ticket