openerp-india team mailing list archive
-
openerp-india team
-
Mailing list archive
-
Message #16542
[Bug 1059210] Re: timed job - lastcall is in the future
we found a basic problem in the design of ir_cron and our own
implementation
we think that only one time source (python) should be taken also for sql
statements instead of psql now() at time zone UTC
after replacing psql now() with %s (python time) the script works fine
** Changed in: openobject-server
Status: Incomplete => New
--
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Server.
https://bugs.launchpad.net/bugs/1059210
Title:
timed job - lastcall is in the future
Status in OpenERP Server:
New
Bug description:
please see screenshot
current time is 8:40 PM
some lastcall values shown in OpenERP are in the future
the select now() shows the correct time of computer and openerp user
could it be that the timed job does not use the timezone of admin to
write the lastcall?
To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/1059210/+subscriptions
References