Data type mapping
This table shows the mapping between LN data types and their SQL Server counterparts.
| Mapping between LN and MSQL data types | ||
|---|---|---|
| LN data types | MSQL data types | |
| For Infor Baan IVc & Baan 5.0 | For Infor LN 1 | |
| CHAR | Tinyint | Integer |
| ENUM | Tinyint | Integer |
| INT | Smallint | Integer |
| LONG | Integer | Integer |
| TIME | DateTime | DateTime |
| TEXT | Integer | Integer |
| BITSET | Integer | Integer |
| FLOAT | Real | Real |
| DOUBLE | Float | Float |
| STRING(N) | Char(n) | Char(n) |
| DATE | DateTime | DateTime |
| BLOB2 | VARBINARY (max) | VARBINARY (max) |
- Default behavior on Infor LN, but configurable to the behavior on Infor Baan IVc/Baan 5.0 .
- The SQL_BINARY type is used to store UUID columns, generated if a table contains a BLOB column (except in Baan IV, where the UUID column is a string column).
By default, the Infor Enterprise Server SQL Server driver uses the VARCHAR data type for these releases:
- Infor Baan 5.2a and later with a 8.4.x porting set version or higher
- Infor Baan 5.0 and later with a 8.7.x porting set version
At LN application level, the data type is interpreted as normal string type, including any trailing spaces. Operations such as comparison and concatenation remain the same for earlier versions, regardless of the string data-type that is used at SQL Server level.