Closed
Bug 631131
Opened 15 years ago
Closed 15 years ago
Python server serves odd floating point values for WBO modified field
Categories
(Cloud Services Graveyard :: Server: Sync, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 631137
People
(Reporter: st3fan, Unassigned)
Details
I'm receiving a WBO from the server that looks like this:
{
u'sortindex': 100,
u'payload': ...,
u'modified': 1296704831.3499999,
u'id': u'kONHOobXLXdx'
}
When I look in the test.db sqlite file on the server I see that modified is set to 129670483135. It looks like a floating point issue when the modified is divided by 100.
>>> 129670483135 / 100.
1296704831.3499999
I confirmed that the above is not a JSON parse issue. The raw response from the server has the same 1296704831.3499999 value.
Comment 1•15 years ago
|
||
(I wished we would use ETags instead of timestamps in Sync)
Several things here:
- The timestamps are stored as big ints in the database - 129670483135
- We should use decimals when we return the value / 100
I'll take care of this in 631137
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Updated•2 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•