Stringified Value Format: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
(2 intermediate revisions by the same user not shown) | |||
Line 32: | Line 32: | ||
|| | || | ||
|- | |- | ||
||small integer (maximum | ||small integer (maximum 2 147 483 647) | ||
||4<number value> | ||4<number value> | ||
|| | || | ||
Line 55: | Line 55: | ||
* 1.3 seconds -> 70.00:00:01.300 | * 1.3 seconds -> 70.00:00:01.300 | ||
* -43 minutes -> 7-0.00:43:00.000 | * -43 minutes -> 7-0.00:43:00.000 | ||
|- | |- | ||
||array | ||array | ||
||[] | ||[ ... ] (same as JSON array where each item uses the stringified format) | ||
|| | || | ||
* empty array -> [] | * empty array -> [] |
Latest revision as of 09:20, 11 December 2024
QPR ProcessAnalyzer uses the stringified value format in filters and expression queries for values appearing in JSON format. The stringified format encodes different types of data into strings that captures both the type and value of the data. The first character in the stringified format represents the type of the data.
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 2 147 483 647) | 4<number value> |
|
large integer | 5<number value> |
|
boolean | 6True or 6False | |
timespan (duration) | 7d.HH:mm:ss.fff |
|
array | [ ... ] (same as JSON array where each item uses the stringified format) |
|