[kronolith] Fix for Kronolith and PostgreSQL 8.3.x

[Marc Balmer]

Am 10.05.2008 um 00:46 schrieb Jan Schneider:

> Zitat von Marc Balmer <marc at msys.ch>:
>
>> The attached diff adds explicit typecasts where needed and makes
>> Kronolith happy on PostgreSQL again.  This should also be safe
>> on MySQL.
>
> We support a few more databases than PostgreSQL and MySQL, even though
> the CAST() statement is part of SQL-92. Does anybody how portable this
> really is?

One problem could be that different types are being used on different
databases, e.g. on PostgreSQL a TIMESTAMP is being used for events
while on MySQL a DATETIME is being used.

I did _not_ test this diff on any other database than PostgreSQL, so it
should not go in as is.