yahoo-eng-team team mailing list archive

[Kevin Benton <1620254@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: neutron
     Importance: Undecided
     Assignee: Kevin Benton (kevinbenton)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Kevin Benton (kevinbenton)

** Changed in: neutron
    Milestone: None => newton-rc1

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1620254

Title:
  OVO DateTimeField is not compatible with our timestamps

Status in neutron:
  New

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1620254/+subscriptions