On Thursday 11 August 2011, Alex Hermann wrote:
> > > In MySQL, one could use the DECIMAL type.
> >
> > there is currently no write functionality in the DB API and also scheme
> > generation XSL to support the DECIMAL type.
>
> IMHO support should be added then. Floating point (on digitial equipm
On Thursday 11 August 2011, Henning Westerholt wrote:
> On Thursday 11 August 2011, Alex Hermann wrote:
> > On Wednesday 10 August 2011 14:21:10 Daniel-Constantin Mierla wrote:
> > > - a new column to store the seconds.milliseconds as double
> >
> > Please don't use double, use a fixed point forma
On Thursday 11 August 2011, Alex Hermann wrote:
> On Wednesday 10 August 2011 14:21:10 Daniel-Constantin Mierla wrote:
> > - a new column to store the seconds.milliseconds as double
>
> Please don't use double, use a fixed point format. Double's are for
> scientific use, this is accounting so exac
On Wednesday 10 August 2011 14:21:10 Daniel-Constantin Mierla wrote:
> - a new column to store the seconds.milliseconds as double
Please don't use double, use a fixed point format. Double's are for scientific
use, this is accounting so exact numbers are required.
In MySQL, one could use the DECI
Hey,
On 10.08.2011 14:21, Daniel-Constantin Mierla wrote:
> it seems that is some parts of the world it is required to have call
> duration with two decimals precision. By default acc module does the
> timestamp in seconds.
>
> Thinking of adding an option to save the milliseconds, I see two opt
Hello,
it seems that is some parts of the world it is required to have call
duration with two decimals precision. By default acc module does the
timestamp in seconds.
Thinking of adding an option to save the milliseconds, I see two option:
- a new column to store the milliseconds part as inte
