Comment 0 for bug 1620254
Revision history for this message
| Kevin Benton (kevinbenton) wrote OVO DateTimeField is not compatible with our timestamps | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
The timestamps we store in the DB do not preserve microseconds because we use the default mysql datetime field which chops them off (or rounds depending on DB connector). This means that the timestamp will lose precision as it's stored in the DB so an object before DB persistence would not be equal to the same object after restored from the DB.
Also, from an API perspective, it creates an inconsistency because 'OVO native' resources that use the common DB to_dict() to generate the API response will include microseconds while the existing resources only return precision in the seconds field.