[ZBXNEXT-651] add "Boolean" data type for "Numeric (unsigned)" value type Created: 2011 Feb 03 Updated: 2011 Dec 22 Resolved: 2011 Mar 29 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Frontend (F), Server (S) |
Affects Version/s: | 1.9.1 (alpha) |
Fix Version/s: | 1.9.3 (alpha) |
Type: | New Feature Request | Priority: | Major |
Reporter: | Aleksandrs Saveljevs | Assignee: | Aleksandrs Saveljevs |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Description |
In addition to "Octal", "Decimal", and "Hexadecimal" data types, we should also have "Boolean" data type. |
Comments |
Comment by Aleksandrs Saveljevs [ 2011 Feb 03 ] |
Development is being done in |
Comment by Aleksandrs Saveljevs [ 2011 Feb 03 ] |
As of r17388, values "true", "t", "yes", "y", "on", "up" (case-insensitive) and non-zero numeric values (including floating point values) count as TRUE. Values "false", "f", "no", "n", "off", "down" (case-insensitive) and a zero numeric value count as FALSE. Boolean values TRUE and FALSE get stored as 1 and 0 in the database, respectively. Suggestions for other values to be treated as TRUE and FALSE are welcome. |
Comment by richlv [ 2011 Feb 03 ] |
other potential values : |
Comment by Aleksandrs Saveljevs [ 2011 Feb 15 ] |
Added. Anything else? |
Comment by Aleksandrs Saveljevs [ 2011 Mar 29 ] |
Available in pre-1.9.3, r18732. |