Commit: ad7be0f55ec7244387b7fb26cc5ed974d0ce2a37
Author: Stan Lagun <email address hidden>
Date: Thu May 5 06:07:21 2016
Increase status report messages time resolution
We use DATETIME SQL type for created/updated columns
everywhere through the database. In SQL standard
DATETIME defaults to DATETIME(6) which is 6 digit
fraction second part. However MySQL defaults it
to DATETIME(0) for backward compatibility. In result
status messages timestamps get rounded to the
second boundary and if there are several status
messages were generated within a second
after table sort they might be shown in a different
order.
This commit adds MySQL migration that increases
resolution for the status table and adds subseconds
to the generated status repor timestamps.
Reviewed: https:/ /review. fuel-infra. org/20342
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka
Commit: ad7be0f55ec7244 387b7fb26cc5ed9 74d0ce2a37
Author: Stan Lagun <email address hidden>
Date: Thu May 5 06:07:21 2016
Increase status report messages time resolution
We use DATETIME SQL type for created/updated columns
everywhere through the database. In SQL standard
DATETIME defaults to DATETIME(6) which is 6 digit
fraction second part. However MySQL defaults it
to DATETIME(0) for backward compatibility. In result
status messages timestamps get rounded to the
second boundary and if there are several status
messages were generated within a second
after table sort they might be shown in a different
order.
This commit adds MySQL migration that increases
resolution for the status table and adds subseconds
to the generated status repor timestamps.
Change-Id: I0ced904063679a 81503c67d426d01 61204b4831b
Related-Bug: #1570932