PowerBuilder
PowerBuilder
Demonstrates how to Handle Large Integers in JSON
See more JSON Examples
Demonstrates how to handle large integers in JSON. (Integers larger than what can fit in a 32-bit signed integer.)Chilkat PowerBuilder Downloads
integer li_rc
integer li_Success
oleobject loo_Json
integer li_Id
string ls_AccountId
li_Success = 0
// Let's say your JSON has this:
// {
// "id": 20000000001234567
// }
loo_Json = create oleobject
li_rc = loo_Json.ConnectToNewObject("Chilkat.JsonObject")
if li_rc < 0 then
destroy loo_Json
MessageBox("Error","Connecting to COM object failed")
return
end if
li_Success = loo_Json.LoadFile("qa_data/json/large_int.json")
if li_Success = 0 then
Write-Debug loo_Json.LastErrorText
destroy loo_Json
return
end if
// The integer is too large for a 32-bit signed integer that is returned by IntOf.
// The result will be something that wrapped around and could be negative.
// In this case it would be: -543893881
li_Id = loo_Json.IntOf("id")
Write-Debug "id: " + string(li_Id)
// The solution is to read the integer value as a string, and then use the features in your programming language
// to convert from a string to a 64-bit integer.
//
// Alternatively, you may wish to simply hold the value as a string. If, for example, the integer simply references
// an order ID, an account ID, etc., then there's no need to convert to an integer value. You're not going to be doing
// mathematical operations on it anyway. This is usually the case for large integers -- they typically exist
// in JSON as an account ID.
// You can get any JSON value as a string:
ls_AccountId = loo_Json.StringOf("id")
Write-Debug "accountId: " + ls_AccountId
// Sample output:
// id: -543893881
// accountId: 20000000001234567
destroy loo_Json