Committed a change that ensures we fall back to the default 
listTimeObjects() behaviour, which is basically returning all the 
objects in a source and then checking them for the proper date range.   
  But, like chuck said, we don't really support mySQL 3 and you'll get 
much better performance from this part of the code (especially with 
large address books) with newer versions of MySQL.

Assigning to Michael for double checking catching this error. But in 
general we don't support MySQL 3.

SUBSTR() is actually the only substring function that works the same 
across all major RDBMs. There are really still people running MySQL 3? 
:-)

@Jan Schneider:



I use mysql 3.23.58.



From mysql Documentation:

`SUBSTR()' is a synonym for `SUBSTRING()', added in MySQL 4.1.1.



Since everything seems to run fine with V3.23 I suggest to simply 
change the SUBSTR to SUBSTRING to get more backwards compatibility.

Which RDBMS do you use?

Wrong SQL detected:

turba/lib/Driver/sql.php:508:



$where = array('sql' => $bday . ' IS NOT NULL AND SUBSTR(' . $bday



should be:



$where = array('sql' => $bday . ' IS NOT NULL AND SUBSTRING(' . $bday