Closed
Bug 702329
Opened 14 years ago
Closed 14 years ago
use BigInteger for timestamps in Balrog
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Unassigned)
References
Details
Attachments
(1 file)
|
1.00 KB,
patch
|
catlee
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
Apparently Integer translate to Integer(11) in MySQL, and because we're multiplying the float timestamps and getting a really big Integer, this isn't big enough.
Attachment #574329 -
Flags: review?(catlee)
|
||
Comment 1•14 years ago
|
||
Comment on attachment 574329 [details] [diff] [review]
use BigInteger
Review of attachment 574329 [details] [diff] [review]:
-----------------------------------------------------------------
::: auslib/db.py
@@ +375,1 @@
> # Timestamps are stored as an Integer, but actually contain
this comment isn't quite accurate now
Attachment #574329 -
Flags: review?(catlee) → review+
|
Reporter | |
Comment 2•14 years ago
|
||
Comment on attachment 574329 [details] [diff] [review]
use BigInteger
Checked in, with comment updates. Jenkins run is here: https://jenkins.mozilla.org/job/Balrog/35/
Attachment #574329 -
Flags: checked-in+
|
|
Reporter | |
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
|
Assignee | |
Updated•13 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•