Closed
Bug 1625450
Opened 5 years ago
Closed 5 years ago
Default application field to 'unspecified' or empty string ''
Categories
(Tree Management :: Perfherder, task, P1)
Tree Management
Perfherder
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: igoldan, Assigned: onegru)
References
Details
Attachments
(1 file)
It's likely this is a one-liner.
Once this gets deployed, it'd be a could idea to let it bake for a day. That way, all active data producers will naturally overwrite the none value with 'unspecified'.
We should even see if we could use the empty string '' instead of 'unspecified', according to Django's official docs:
Avoid using null on string-based fields such as CharField and TextField. If a string-based field has null=True, that means it has two possible values for “no data”: NULL, and the empty string. In most cases, it’s redundant to have two possible values for “no data;” the Django convention is to use the empty string, not NULL.
|
Reporter | |
Updated•5 years ago
|
Summary: Default application field to 'unspecified' → Default application field to 'unspecified' or empty string ''
|
|
Reporter | |
Updated•5 years ago
|
Component: Raptor → Perfherder
Product: Testing → Tree Management
Version: Version 3 → ---
|
||
Comment 1•5 years ago
|
||
|
|
Reporter | |
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•