commit 89a4c4cb5af9b22ef07ea5f1ddcff6edd4997623
Author: Stan Lagun <email address hidden>
Date: Fri Apr 29 00:33:34 2016 -0700
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. openstack. org/311045 /git.openstack. org/cgit/ openstack/ murano/ commit/ ?id=89a4c4cb5af 9b22ef07ea5f1dd cff6edd4997623
Committed: https:/
Submitter: Jenkins
Branch: master
commit 89a4c4cb5af9b22 ef07ea5f1ddcff6 edd4997623
Author: Stan Lagun <email address hidden>
Date: Fri Apr 29 00:33:34 2016 -0700
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: Ice8c2d82c6a320 c7f73c27f4c60c8 7bef55b8d95
Related-Bug: #1462270