Common functional restrictions

Floating point type values may be calculated in error (cancelation of significant digits or loss of trailing digits) when calculation or writing to another system is performed.

Examples:

• If you input "0.05" and "0.01" to the Mapper Number > Calculation > Add logic, the data output is "0.060000000000000005".

• If you input "1.2345678901234567" and "100000000" to the Mapper Number > Calculation > Add logic, the data output is "1.000000012345679e+08".

• If you write the floating point type "9223372036854775000.0" to the BIGINT type column of SQL Server, the value becomes "9223372036854774784" due to processing by HULFT IoT EdgeStreaming.

• If you write the floating point type "922337203685477.5807" to the Money type column of SQL Server, the following error occurs, and writing cannot be performed:

  could not exec statement: mssql: value = 922337203685477.620000 in money type causes an arithmetic overflow error.

• If you write the floating point type "92233720368547758.07" to the Money type column of PostgreSQL, the following error occurs, and writing cannot be performed:

  pq: value \"92233720368547760\" is out of range for type money

• If you write the floating point type "9223372036854775000.0" to the BIGINT type column of MySQL, the value becomes "9223372036854774784" due to processing by HULFT IoT EdgeStreaming.

  If you write the floating point type "9223372036854776000.0", the value becomes "9223372036854775807".

The maximum and minimum values for integer type are as follows:

Maximum: 9223372036854775807

Minimum: -9223372036854775808

If the Mapper calculation result exceeds the maximum value, the calculation result value overflows.

If the calculation result is lower than the minimum value, the calculation result value underflows.

The maximum and minimum values for floating point type are as follows:

Maximum: 1.7976931348623157e+308

Minimum: -1.7976931348623157e+308

If the Mapper calculation result exceeds the maximum value, the calculation result value overflows.

If the calculation result is lower than the minimum value, the calculation result value underflows.

The value may be calculated in error (cancelation of significant digits or loss of trailing digits) when calculation is performed.

If you change Global Resource Settings on Control Panel while the script is open on the Designer screen, when you execute the script that was open, any changes made to Global Resource Settings are not reflected.

When you make changes to Global Resource Settings, be sure to close and reopen the Designer screen before you execute the script.

Specific words cannot be used to specify the following target field names on the designer screen.

Target field names

• Project name

• Script name

• Script variable name

• Icon name

• Input/Output schema node name

For details about specific words, refer to Specific words.

If you perform debugging with the following settings configured, the script variable value is not displayed in the Debug information view:

• From the Designer screen, select Build > Build script and deploy it on a remote device menu

On the Properties screen for each adapter, you cannot specify script variables for any of the specifiable fields.

If you specify a floating point value as the input data for the following logic, all digits after the decimal point are truncated, and only the integer part undergoes zero padding:

• The Mapper String > Calculation > Zero padding logic