[SR-Users] rfc: accounting records time details

[Daniel-Constantin Mierla]

Hello,

On 4/29/13 11:47 AM, Thilo Bangert wrote:
>> More suggestions? Pro or cons opinions?
> I'd just save one timestamp, ie TAI64 or as java does miliseconds since epoch,
> in a single, new field. saving the timestamp in two fields seems messy.
it can be one field only, it is a matter of module parameters.

> miliseconds since epoch is probably preferable, since it can be converted to
> human readable dates by the database server.
miliseconds is cutting from the precision that is get inside. Also have 
in mind that there are many database connectors, not only mysql.

>
> then have a flag that may be enabled, which additionally saves the time in the
> current format (with less precision) -- for backward compatability.
>
> but a change like this i'd save for a 5.0 release.
the plan is to get it for 4.1.0, 5.0.0 looks a bit far away at this moment.

Cheers,
Daniel

>
> kind regards
> Thilo
>
>> Cheers,
>> Daniel
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, San Francisco, USA - June 24-27, 2013
   * http://asipto.com/u/katu *