Both TurboIMAGE/XL and IMAGE/SQL have data types that do not map
exactly to a type in the other system. However, a satisfactory
mapping with appropriate conversions can easily be done for most
TurboIMAGE/XL data types.
Basic Mapping |
 |
Table 3-2 “Mapping of TurboIMAGE/XL and IMAGE/SQL Data Types”
shows the mapping of the most common data types from TurboIMAGE/XL to
IMAGE/SQL:
Table 3-2 Mapping of TurboIMAGE/XL and IMAGE/SQL Data Types
| TurboIMAGE/XL Data Type | IMAGE/SQL Data Type | Description |
|---|
| I,J | SMALLINT | 16-bit integer |
| I2,J2 | INTEGER | 32-bit integer |
| K1,K2 | INTEGER | Requires conversion from binary to integer |
| Pn | DECIMAL(n-1,0) | Packed decimal |
| R4 | FLOAT | Conversion from HP 3000 real to IEEE real |
| U(n), X(n) | CHAR(n) | Byte character string |
| Zn | DECIMAL(n,0) | Requires conversion from zoned decimal to packed
decimal
|
Compound Items |
|
TurboIMAGE/XL compound items are not compatible with IMAGE/SQL data
types because IMAGE/SQL does not accomodate arrays.
In IMAGE/SQL, you need to create a separate column description for
each member of the compound item.
Default Values |
|
Default values indicate the absence of a value.
IMAGE/SQL assigns the missing field
an empty string (a blank) for character values
or a zero for numeric values.
TurboIMAGE/XL items are always defined in IMAGE/SQL with the NOT NULL
and default value specification.
