Stringified Value Format: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 32: | Line 32: | ||
|| | || | ||
|- | |- | ||
||small integer (maximum | ||small integer (maximum allowed value 2 147 483 647) | ||
||4<number value> | ||4<number value> | ||
|| | || |
Latest revision as of 10:25, 2 November 2022
QPR ProcessAnalyzer uses the stringified value format in filters and expression queries when values are defined in the JSON format. The stringified format encodes different types of data into a string format that captures both the type and value of the data. The first character in the stringified format represent the type of the data. The conversion is needed because JSON only supports strings, numbers and booleans.
The stringification is done for each data type according to following rules:
Data type | Format | Example |
---|---|---|
string | 0<string value> |
|
decimal number (float) | 1<decimal value> |
|
date | 2yyyy-MM-ddTHH:mm:ss.fff |
|
null value | 3 | |
small integer (maximum allowed value 2 147 483 647) | 4<number value> |
|
large integer | 5<number value> |
|
boolean | 6True or 6False | |
timespan (duration) | 7d.HH:mm:ss.fff |
|