openerp-india team mailing list archive

[wowas <1002639@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

In All statistical reports, that use extract Date, Month and etc. from
timestamp, there are an error on the border of days.

For example in "crm\report\crm_lead_report.py":

                    to_char(c.create_date, 'YYYY') as creation_year,
                    to_char(c.create_date, 'MM') as creation_month,
                    to_char(c.create_date, 'YYYY-MM-DD') as creation_day,

don't worry about timezone and convert to year, month and day in UTC time.
But if we have stored date 2012-05-31 23:00:00 and our time zone +4hours we get ERRORs from such convertions.
Local time must be 2012-06-01 03:00:00 and expected day - 1 JUNE, but we get day (for this record) - 31 MAY.

** Affects: openobject-addons
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/1002639

Title:
  [6.1] TimeZone ERRORs in statistical reports

Status in OpenERP Addons (modules):
  New

Bug description:
  In All statistical reports, that use extract Date, Month and etc. from
  timestamp, there are an error on the border of days.

  For example in "crm\report\crm_lead_report.py":

                      to_char(c.create_date, 'YYYY') as creation_year,
                      to_char(c.create_date, 'MM') as creation_month,
                      to_char(c.create_date, 'YYYY-MM-DD') as creation_day,

  don't worry about timezone and convert to year, month and day in UTC time.
  But if we have stored date 2012-05-31 23:00:00 and our time zone +4hours we get ERRORs from such convertions.
  Local time must be 2012-06-01 03:00:00 and expected day - 1 JUNE, but we get day (for this record) - 31 MAY.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/1002639/+subscriptions