Stringified Value Format: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 32: | Line 32: | ||
|| | || | ||
|- | |- | ||
||small integer | ||small integer (at maximum 2 147 483 647) | ||
||4<number value> | ||4<number value> | ||
|| | || | ||
Line 41: | Line 41: | ||
||5<number value> | ||5<number value> | ||
|| | || | ||
* 3000000000 -> 53000000000 | |||
* -12345678900 -> 5-12345678900 | |||
|- | |- | ||
||boolean | ||boolean |
Revision as of 10:32, 29 October 2020
QPR ProcessAnalyzer uses the stringified value format in filters when they are defined using the JSON format. The stringified format encodes data of different types into a string format. This conversion is needed because a pure 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 | 1<decimal value> |
|
date | 2yyyy-MM-ddTHH:mm:ss.fff |
|
null value | 3 | |
small integer (at maximum 2 147 483 647) | 4<number value> |
|
large integer | 5<number value> |
|
boolean | 6True or 6False | |
timespan | 7d.HH:mm:ss.fff |
|