Handling data loss in data type conversions

Special attention must be given to mapping data types between Langstack and MS-SQL when the two types are not accurately compatible as this may cause data loss or overflow if one of the data types contains a larger value than the mapped-to data type can handle.

In case of data loss due to an overflow while reading from MSSQL to Langstack, if any default value is defined by the user in the ETL Field Mapping then it will be used, else Langstack default values will be used.

In case of data loss due to an overflow, while writing from Langstack to MSSQL, the row will be skipped and the 'On Skipped' function is triggered and the 'skippedReason' variable is set with "Data overflow".

In the case of mapping of approximate numeric types i.e. float and real data types between Langstack and MS-SQL, the mapped values may not have the exact accuracy.