|
From: Robert M. <rob...@gm...> - 2011-11-09 12:51:08
|
On Tue, Nov 8, 2011 at 10:50 PM, Paul Richards <pa...@ma...> wrote: > David/Rob: your both slightly wrong here from what I recall of what I > originally implemented, and what then happened in trunk [dhx: remember your > fixes to redhat crapiness] > I personally feel this is probably something we should ensure is fixed for > the next major release of mantis as opposed trying to "bugfix" in now. > > To put another way, it would be nice to look at getting a 1.3/2.0/name > 'alpha' out around December/January time - as the focus to this would seem > to be a mixture of work to DB Api, Objects, Exceptions, Templating, New > webservice api as 'ideas/work in progress', now is probably not a good time > to do patches to adodb/mantis to change how we store timestamps. Here's my simple test: 1. On a bugtracker instance, running in Europe/Bucharest time mode, I have the following data in the database mysql> select date_submitted, from_unixtime(date_submitted) from mantis_bug_table where id = 4; +----------------+-------------------------------+ | date_submitted | from_unixtime(date_submitted) | +----------------+-------------------------------+ | 1300003755 | 2011-03-13 10:09:15 | +----------------+-------------------------------+ 2. I have set my Mantis user's time zone to Europe/Bucharest 3. I have viewed the bug in the web interface The creation date shown is 2011-03-13 10:09 Therefore the database will store the times in the local time zone, and not in UTC . When the next major release is available, I will be happy to update the SOAP API to be in line with the core APIs . Until then, I will adjust the SOAP API to remove this offset and send times in GMT. Thanks, Robert > > Paul > On Tue, Nov 8, 2011 at 1:15 PM, David Hicks <d...@hx...> wrote: >> >> On Tue, 2011-11-08 at 15:07 +0200, Robert Munteanu wrote: >> > Are you sure that the time in the database is set in UTC? If that's >> > true, I'm trying to solve a problem which does not exist. >> >> Perhaps not in every case. I only checked the function in bug_api that >> is called to insert a new issue into the database - and I only checked >> against the submission timestamp field. >> >> The SOAP API or other parts of MantisBT may feed in something other than >> db_now() or time() for timestamps. It might be worth grepping the source >> code for SQL statements that refer to timestamp columns and working >> backwards to ensure that db_now() or time() is being used to provide the >> value. >> >> >> ------------------------------------------------------------------------------ >> RSA(R) Conference 2012 >> Save $700 by Nov 18 >> Register now >> http://p.sf.net/sfu/rsa-sfdev2dev1 >> _______________________________________________ >> mantisbt-dev mailing list >> man...@li... >> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev >> > > > ------------------------------------------------------------------------------ > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > > -- Sent from my (old) computer |