Data type mapping
This table shows the mapping between LN data types and their Oracle counterparts:
| Mapping between LN and Oracle data types | |
|---|---|
| LN data type | Oracle data type |
| Byte | NUMBER |
| Enumerated | NUMBER |
| Integer | NUMBER |
| Long | NUMBER |
| UTC Date/Time | DATE (1) |
| Text | NUMBER |
| (Bit)Set | NUMBER |
| Float | NUMBER |
| Double | NUMBER |
| String | CHAR(n)/VARCHAR(n)
NCHAR(n)/NVARCHAR(n) (2 or 3) |
| TSS string |
CHAR(n)/VARCHAR(n) NCHAR(n)/NVARCHAR(n) (2 or 3) |
| Date | DATE (1) |
| Raw | RAW |
| Blob | BLOB |
| (4) | RAW |
- The empty date and utc timestamp is represented in Oracle as January 1, 4712 B.C 00:00:00.
- The LN Oracle
driver can use either the ANSI-compliant CHAR(n) Oracle data type or the VARCHAR2(n)
Oracle data type. This is controlled by the resource ora_use_varchar.
For more information on the conversion from a CHAR(n) based database to a VARCHAR2(n) based database, see Conversion from CHAR to VARCHAR2 strings.
- If LN is installed in Unicode mode, the LN Oracle driver uses the Oracle NCHAR or NVARCHAR2 data type.
- The Oracle RAW type is used to store compressed array columns and UUIDs generated if the Multilanguage Application Data feature is used or if a table has one or more BLOB colums (except in Infor Baan IVc, where the UUID column is a string column).