Morgan Fainberg 66a1047e8c Add int storage of datetime for password created/expires ... Due to MySQL (in some versions) not storing datetime resolution below one second, keystone occasionally ends up with weird behavior such as a New password not being valid. The password created at and expires at columns now store both datetime (for rolling upgrades) and integers. Keystone from Pike and beyond leans on the new created_at_int column and expires_at_int column. Change-Id: I2c219b4b9b353f1e2cce6088849a773196f0e443 Closes-Bug: #1702211		2017-08-15 18:34:20 +00:00
..
contract_repo	Add int storage of datetime for password created/expires	2017-08-15 18:34:20 +00:00
data_migration_repo	Add int storage of datetime for password created/expires	2017-08-15 18:34:20 +00:00
expand_repo	Add int storage of datetime for password created/expires	2017-08-15 18:34:20 +00:00
migrate_repo	Remove log translations in keystone	2017-03-25 18:17:15 +00:00
__init__.py	Safer noqa handling	2014-03-27 18:52:07 -05:00
core.py	Add int storage of datetime for password created/expires	2017-08-15 18:34:20 +00:00
upgrades.py	Validate rolling upgrade is run in order	2017-06-27 20:54:04 +00:00