29 Apr
2013
29 Apr
'13
8:03 a.m.
Hi,
On 04/29/2013 01:42 PM, Alex Hermann wrote:
On Monday 29 April 2013 11:05:36 Daniel-Constantin
Mierla wrote:
Just for clarification, we're using DECIMAL(13,3) with the patch on the
tracker, not DOUBLE. What's missing in this patch is the table
definition, so it needs to be updated in any case.
Andreas
1) store seconds.miliseconds as double - there is
a patch (which
Please do not use floating point respresentations for values that will be used
in accounting. Floating point is imprecise. As the time related columns will
most probably be used for billing, the values should be exact. In SQL this
means using the DECIMAL or NUMERIC column type.