07b07d5b83
We've already converted Password objects to use the DateTimeInt format for its datetime attributes[1]. This was necessary to cope with differences in date storage formats between different DBMSs that was causing intermittent test failures. While we're not experiencing those CI problems any more, the DateTimeInt format is the way forward for consistent datetime storage. This patch converts the trust table and model to use the new format. [1] https://review.openstack.org/#/c/493259/ Related-bug: #1702211 Change-Id: If524c743170924e5b8cfdafa862ed31b06db018c
9 lines
334 B
YAML
9 lines
334 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
The trusts table now has an expires_at_int column that represents the
|
|
expiration time as an integer instead of a datetime object. This will
|
|
prevent rounding errors related to the way date objects are stored in some
|
|
versions of MySQL. The expires_at column remains, but will be dropped in
|
|
Rocky.
|