Remove SQL's datetime format inplace of integer timestamps
Bug #1513538 reported by
Lance Bragstad
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Keystone's current schema uses SQL's DATETIME format. Depending on the version of SQL (before or after v5.6.4), it may or may not support sub-second accuracy/precision.
> A DATETIME or TIMESTAMP value can include a trailing fractional seconds part in up to microseconds (6 digits) precision. In particular, as of MySQL 5.6.4, any fractional part in a value inserted into a DATETIME or TIMESTAMP column is stored rather than discarded.
Source: https:/
We should replace keystone's use of DATETIME with an integer timestamp. With integer timestamps we can support sub-second accuracy regardless of the version of SQL being used.
description: | updated |
tags: | added: sql |
description: | updated |
description: | updated |
Changed in keystone: | |
assignee: | Lance Bragstad (lbragstad) → Adam Young (ayoung) |
Changed in keystone: | |
assignee: | Adam Young (ayoung) → Lance Bragstad (lbragstad) |
Changed in keystone: | |
assignee: | Lance Bragstad (lbragstad) → Boris Bobrov (bbobrov) |
Changed in keystone: | |
assignee: | nobody → Lance Bragstad (lbragstad) |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/243742
Review: https:/