[OpenSIPS-Users] Best practices inquiry: database timezone

[Vasil Kolev]

В 10:19 -0400 на 31.03.2009 (вт), Phil Vandry написа:
> On Tue, Mar 31, 2009 at 12:18:34PM +0300, Vasil Kolev wrote:
> > In my experience (which is mostly postgres) the local type "timestamp
> > with timezone" is what you need - it records the date in UTC with the
> > timezone it was in, so in the end you always have the UTC time and can
> 
> That's a good idea, but OpenSIPS does not currently supply the
> information to the database to make good use of that data type. It
> converts its internal representation (time_t, which is UTC time as an
> integer) to a string in the format "YYYY-mm-dd HH:MM:SS" in local time
> and gives that string to the database.
> 

Haven't checked the module which does this, but using the time from
opensips is not a good idea anyway, I've always use the time in the
database. So, mostly, insert into call(start_time) values (NOW()), and
then update call set end_time=NOW().... This way you also know that
you're talking to one clock (as you can have more than one instance of
opensips running).


-- 
Regards,
Vasil Kolev
Attractel NV
dCAP #1324, LPIC2