timetrex and mysql timezone support

[mrworldcup]

Hello,

I'm tasked with installing timetrex and evaluating it for potential long term use (which also means i would be the one keeping it running stable if we decide to purchase and host it here

We have a small team, we provide mysql support and we haven't been offering postgresql which is why I'm writing this thread to get more information:


One question:
As developers of timetrex, and from a developer perspective of maintaining and troubleshooting code related to mysql and all-things-timezone, how would you say mysql support for timezone functionality is *today*? What are your opinions?

Do you feel it's robust?
Is it on par with postgresql in this area?
Are there shortcomings? still? how serious?
Does it require some extra-maintenance?

That's what I'd like to know.




According to the forum it seems there used to be (are there still???) some significant problems with mysql's timezone support. In thread [1] back in 2007 I think 2 bugs were identified in that thread, both [1a] and [1b]. How about these days?


[1]
TimeTrex Time and Attendance • View topic - WARNING: MySQL v5.0.37 and higher is broken!:
http://forums.timetrex.com/viewtopic.php?t=298

[1a]
MySQL Bugs: #28336: Date comparison changed, not mentioned in manual:
http://bugs.mysql.com/bug.php?id=28336

[1b]
MySQL Bugs: #28936: Group by returning incorrect values when sub-query is involved
http://bugs.mysql.com/bug.php?id=28936

[shaunw]

Nothing has changed, MySQL's timezone support is virtually non-existent, and what does exist is horrible at best. The simple fact that it doesn't even have a "timestamp with timezone" datatype, which every other serious database has, tells a lot. Because of this it actually isn't even safe to use in a multi-timezone, multi-user application which TimeTrex of course is. This is just one reason why we don't recommend using MySQL if at all possible.

There are many other reasons too, stability is a problem, speed is a big problem with about 50 or more employees because of complex queries that MySQL's query planner has no idea how to handle. It also lacks many advanced features that are extremely helpful in reporting which restricts what we can offer to MySQL users.

[mrworldcup]

Thanks for responding! I found this helpful

Please feel free to update this thread as time goes on and mysql changes (whether it changes either positively or negatively... I'd be curious and i'm sure others would be too.).