Avoid negative zero for results when converting time to decimal.
This is a followup patch to
Bug#18411494 WRONG COMPARSION ON BIG DECIMAL VALUES