Stringified Value Format: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
||0 | ||0 | ||
||0<string value> | ||0<string value> | ||
||Patricia White -> 0Patricia White | || | ||
* Patricia White -> 0Patricia White | |||
|- | |- | ||
||decimal number | ||decimal number | ||
| Line 49: | Line 50: | ||
* 2 days -> 72.00:00:00.000 | * 2 days -> 72.00:00:00.000 | ||
* 6 hours -> 70.06:00:00.000 | * 6 hours -> 70.06:00:00.000 | ||
* 1.3 seconds 70.00:00:01.300 | * 1.3 seconds -> 70.00:00:01.300 | ||
|} | |} | ||
Revision as of 22:43, 28 October 2020
QPR ProcessAnalyzer uses the stringified value format in several places when filters are defined using the JSON format. The stringified format encodes data of different types into a string format (which is supported by JSON format).
The stringification is done according to following rules:
| Data type | Prefix | Format | Example |
|---|---|---|---|
| string | 0 | 0<string value> |
|
| decimal number | 1 | ||
| date | 2 | 2yyyy-MM-ddTHH:mm:ss.fff | |
| null value | 3 | 3 (means null value) | |
| Small integer | 4 | ||
| Large integer | 5 | ||
| boolean | 6 | 6True or 6False | |
| timespan | 7 | 7d.HH:mm:ss.fff |
|