Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
slapos slapos
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 122
    • Merge requests 122
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slaposslapos
  • Merge requests
  • !623

Merged
Created Sep 13, 2019 by Jérome Perrin@jeromeOwner

erp5: set mariadb timezone to UTC

  • Overview 5
  • Commits 1
  • Changes 2

ERP5Catalog assumes that dates in catalog are UTC, this works fine with DATETIME columns that does not carry any timezone information, but TIMESTAMP columns are converted to mariadb timezone, which is by default system timezone.

If we want ERP5Catalog to query on TIMESTAMP columns with the existing logic of converting dates to UTC (because "dates are in UTC in catalog"), we need to have TIMESTAMP columns in UTC.

This also generally seem a better default than falling back to system timezone.

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: fix/erp5-mysql-utc
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7