summaryrefslogtreecommitdiff
path: root/odoo/tools/date_utils.py
AgeCommit message (Collapse)Author
2019-04-03[FIX] tools: February 28thNicolas Martinelli
- Set your fiscal year end date to 28th February - Run the P&L a year before a leap year, e.g. anytime between March 1st and December 31st 2019. - Select 'Last Financial Year' The dates are set from 2019-03-01 to 2019-02-28. There are actually 2 bugs. The one solved here is the following inconsistency: ``` current_date = type(date)(2019, 4, 3) date_utils.get_fiscal_year(current_date, day=28, month=2) 'date_from': datetime.date(2019, 3, 1), 'date_to': datetime.date(2020, 2, 28) current_date = type(date)(2020, 2, 28) date_utils.get_fiscal_year(current_date, day=28, month=2) {'date_from': datetime.date(2019, 3, 1), 'date_to': datetime.date(2020, 2, 29)} ``` Both should return `'date_to': datetime.date(2020, 2, 29)`. This implies that the period is recognized as `custom`, which is affected by the bug solved in PR https://github.com/odoo/enterprise/pull/4006 opw-1949628 closes odoo/odoo#32366 Signed-off-by: Nicolas Martinelli (nim) <nim@odoo.com>
2019-01-03[FIX] tools/date_utils: Fix get_fiscal_year with leap yearsLaurent Smet
Suppose calling get_fiscal_year(date, day=29, month=2) with date(year=2017, month=2, day=28) The computation steps are: date_from = date(year=2017, month=2, day=28) - 1 year = date(year=2016, month=2, day=28) date_from = date_from + 1 day = date(year=2016, month=2, day=29) It's incorrect because the value of date_from must be date(year=2016, month=3, day=1) closes odoo/odoo#29416
2018-08-10[IMP] orm: add support to fill temporal holes (read_group)Francois Volral
This commit add an extra parameter 'fill_temporal' to read_group which allows the orm to add missing groups for date intervals. This is useful for charts. Suppose that we are in a use case where data are grouped by a date fields (typically months but it could be another interval) and displayed in a Bar Chart or a Line Char. Let's says a request has to group records by month for August, September and ...December. If we don't changed anything, we would get a Bar Chart looking like this : ___ ___ | | | | | | | | ___ | | | || || | |___||___||___| Aug Sep D December follows directly after September, it can be unintuitive for the user, so we change that. We add some fake records for each missing months between the earliest and the lastest date of the result ___ ___ | | | | | | | | ___ | | | || | | | |___||___| ___ ___ |___| Aug Sep Oct Nov Dec This commit is part of task #1835644
2018-08-06[REF] *: use native date/datetime for Date/Datetime fieldsRaphael Collet
From this commit onwards, Date fields will return datetime.date objects and Datetime fields will return datetime.datetime objects, this implies a number of things that are clearly explained both in the ORM API for master. This commit also introduces a number of helper functions for dates and datetimes that are exposed in tools.date_utils and fields.Date[time], explained in the documentation as well. Task-ID: 47189
2018-05-30[IMP] account: add account.fiscalyear modelLaurent Smet
In order to improve the fiscal year management, we allow the user to define custom fiscal years using the account.fiscalyear model. Was task: https://www.odoo.com/web#id=39878&view_type=form&model=project.task&menu_id= Was PR #20936