6.0.0-alpha12
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
6/12/25
H
istory
A
ttachments
C
omment
W
atch
Download
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
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers