Fri, 10 Apr 2026 12:09:57 +0000 https://bugs.horde.org/ticket/11064 Turba Browse is very inefficient 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. Fri, 09 Mar 2012 20:01:23 +0000 https://bugs.horde.org/ticket/11064#t70657 > 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. Fri, 09 Mar 2012 20:09:58 +0000 https://bugs.horde.org/ticket/11064#t70658 >> 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. Fri, 09 Mar 2012 20:20:31 +0000 https://bugs.horde.org/ticket/11064#t70660 The actual problem is that 1) name fields are usually composite fields and 2) there is the user preference that defines the name format for sorting. For the filtering to reliably work, this would require composing the fields on the database level. I doubt this is going to be possible in a portable way. Thu, 05 Apr 2012 17:01:24 +0000 https://bugs.horde.org/ticket/11064#t71094 Going to reject, since Jan says this is not going to be possible with current code. Wed, 27 Jun 2012 21:07:52 +0000 https://bugs.horde.org/ticket/11064#t71663