[Tickets #5825] Re: Efficiency enhancements from Kronolith to Turba

[bugs at bugs.horde.org]

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

Ticket URL: http://dev.horde.org/horde/whups/ticket/?id=5825
-----------------------------------------------------------------------
 Ticket             | 5825
 Updated By         | Chuck Hagenbuch <chuck at horde.org>
 Summary            | Efficiency enhancements from Kronolith to Turba
 Queue              | Turba
 Version            | HEAD
 Type               | Enhancement
 State              | New
 Priority           | 2. Medium
 Owners             | 
-----------------------------------------------------------------------


Chuck Hagenbuch <chuck at horde.org> (2007-10-22 21:17) wrote:

> This is a good idea, but makes an assumption that all the backends 
> that Turba supports is able to hande such queries...which is not the 
> case.  We could override the Turba_Driver::listBirthdays() method in 
> (for example) the sql driver, but then we would *still* be making an 
> assumption that every install will have a turba_objects table 
> containing a birthday column - which is also not always true...guess 
> we could somehow check for the existence of a configured birthday 
> column first?

Not sure why we need that assumption - if the source doesn't have a field
that maps to Turba's birthday attribute then listBirthdays should be a
no-op, for starters. Seems reasonable that overriding listBirthdays should
allow a more efficient backend-specific search. I do see a hitch doing date
comparisons in the backend ... but we can format the search dates for the
backend so even that should be fine.