Okay, no problem. To be fair, I think only $dateTime->getTimestamp() requires >=5.3, so it would be possible to work around that some more and it should work >=5.2. If you like, I'll give it a try, but I don't know if >=5.2 still would be acceptable for you.
Anyway, if anybody's interested and is already running PHP 5.3, my branch is a bit more edgy:
1. switched to innoDB (temporarily disabling full-text searching, will add this by sphinx in future)
2. added the above fix for dates
3. and rewritten more functions for dates (now showing proper list of timezones when configuring the user)
4. some other small fixes like setting static memory_limit which was sometimes not enough
Soon more performance fixes, such as changing the MySQL row counting scheme to a quicker one, cause the current one with 700k issues was taking 8 seconds to complete, so for now on our production server we just put a static number there and the list.php loads 3-5 times faster than before.
Okay, no problem. To be fair, I think only $dateTime- >getTimestamp( ) requires >=5.3, so it would be possible to work around that some more and it should work >=5.2. If you like, I'll give it a try, but I don't know if >=5.2 still would be acceptable for you.
Anyway, if anybody's interested and is already running PHP 5.3, my branch is a bit more edgy:
1. switched to innoDB (temporarily disabling full-text searching, will add this by sphinx in future)
2. added the above fix for dates
3. and rewritten more functions for dates (now showing proper list of timezones when configuring the user)
4. some other small fixes like setting static memory_limit which was sometimes not enough
Soon more performance fixes, such as changing the MySQL row counting scheme to a quicker one, cause the current one with 700k issues was taking 8 seconds to complete, so for now on our production server we just put a static number there and the list.php loads 3-5 times faster than before.
http:// bazaar. launchpad. net/~bart8472/ eventum/ hugedb_ edge/