Skip to main content

Beta License: AGPL-3 OCA/server-tools Translate me on Weblate Try me on Runbot

This module provides base classes and models to manage time windows through time.window.mixin.

Table of contents

Usage

Example implementation for the mixin can be found in module test_base_time_window.

As a time window will always be linked to a related model thourgh a M2o relation, when defining the new model inheriting the mixin, one should pay attention to the following points in order to have the overlapping check work properly:

  • Define class property _overlap_check_field: This must state the M2o field to use for the to check of overlapping time window records linked to a specific record of the related model.

  • Add the M2o field to the related model in the api.constrains:

For example:

class PartnerTimeWindow(models.Model):
    _name = 'partner.time.window'
    _inherit = 'time.window.mixin'

    partner_id = fields.Many2one(
        res.partner', required=True, index=True, ondelete='cascade'
    )

    _overlap_check_field = 'partner_id'

    @api.constrains('partner_id')
    def check_window_no_overlaps(self):
        return super().check_window_no_overlaps()

Known issues / Roadmap

  • Storing times using float_time widget requires extra processing to ensure computations are done in the right timezone, because the value is not stored as UTC in the database, and must therefore be related to a tz field.

    float_time in this sense should only be used for durations and not for a “point in time” as this is always needs a Date for a timezone conversion to be done properly. (Because a conversion from UTC to e.g. Europe/Brussels won’t give the same result in winter or summer because of Daylight Saving Time).

    Therefore the right move would be to use a resource.calendar to define time windows using Datetime with recurrences.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • ACSONE SA/NV

  • Camptocamp

Contributors

Trobz

Other credits

The development of this module has been financially supported by:

  • Camptocamp

Maintainers

This module is maintained by the OCA.

Odoo Community Association

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

This module is part of the OCA/server-tools project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Metadata

Release files for odoo14-addon-base-time-window 14.0.1.0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for odoo14-addon-base-time-window 14.0.1.0.1
File Interpreter ABI Platform Actions
odoo14_addon_base_time_window-14.0.1.0.1-py3-none-any.whl Python 3 none any Details for odoo14_addon_base_time_window-14.0.1.0.1-py3-none-any.whl

Release files / odoo14_addon_base_time_window-14.0.1.0.1-py3-none-any.whl

Download URL odoo14_addon_base_time_window-14.0.1.0.1-py3-none-any.whl
Size 28.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7de3e5b308bead14706c00965c573b5cbf5d81531b58d5a9feace73811d5a6ec
BLAKE2b-256 checksum
How to use checksums
a841c1c5e1d1f5b6e0ba9e304e0c57ee42972a600ca4049c20ea274ea448c384
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/60.3.1 requests-toolbelt/0.9.1 tqdm/4.58.0 CPython/3.8.5

Security for odoo14-addon-base-time-window 14.0.1.0.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page