Calculate timestamps within DB, not client
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslo.db |
In Progress
|
Wishlist
|
Yikun Jiang |
Bug Description
Calculating the timestamp in the clients can lead to problems because network latency is variable, clients experience slightly different clock drift.
SQLAlchemy allows us to do this by passing func.now() which tells the DB to calculate the timestamp itself
So, in order to make the updated_at and created_at more accurate, we should calculate the timestamp in db.[1]
[1] https:/
[2] https:/
[3] https:/
[4] http://
Changed in oslo.db: | |
assignee: | nobody → Yikun Jiang (yikunkero) |
status: | New → In Progress |
Changed in oslo.db: | |
importance: | Undecided → Wishlist |
Change abandoned by Stephen Finucane (<email address hidden>) on branch: master /review. opendev. org/592304
Review: https:/