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

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