jsonO returned the following:
jsonO (
jsonOp ( "chip_number" ; "3.56E+14")
)
//{ "chip_number":3.56E+14 }
A user imported microchip numbers in from Excel to a text field. Some of the values Excel reformatted as exponential format. These ended up in the FMGo file.
jsonO assumed this was a number and doesn't add the quotes. The PostGreSQL server was expecting a varchar(45) but rejected this because of the E+ not being within quotations.
Are you able to catch for this or can you add another parameter for jsonO to force the output type. Which might also save time when testing if 'req is too long to be a number'.
jsonO returned the following:
jsonO (
jsonOp ( "chip_number" ; "3.56E+14")
)
//{ "chip_number":3.56E+14 }
A user imported microchip numbers in from Excel to a text field. Some of the values Excel reformatted as exponential format. These ended up in the FMGo file.
jsonO assumed this was a number and doesn't add the quotes. The PostGreSQL server was expecting a varchar(45) but rejected this because of the E+ not being within quotations.
Are you able to catch for this or can you add another parameter for jsonO to force the output type. Which might also save time when testing if 'req is too long to be a number'.