This is an old revision of the document!
Overview | Environments | Databases | Tables | Constraints | Datatypes | Queries | Updates | Example
Omnidex supports most Oracle datatypes; however, care must be taken when mapping the Oracle datatypes to Omnidex.
Most Oracle binary data is stored in NUMBER datatypes. If the NUMBER datatype is accompanied by scale and precision information, Omnidex can guess at an appropriate matching binary datatype, such as BIGINT, INTEGER, SMALLINT, TINYINT, FLOAT or DOUBLE. If scale and precision are not specified, Omnidex will necessarily use a DOUBLE datatype. For the best performance and ease of development, these datatypes should be changed to the smallest binary datatype that will accommodate the values in the column.
Oracle National Character datatypes, which are commonly used to store Unicode data, are shown as CHARACTER or STRING datatype, as these are the most universal datatypes in an Omnidex application. If necessary, these can be changed to Omnidex NCHARACTER or NSTRING datatypes.
Omnidex does not support many of the Oracle LOB datatypes, though Oracle CLOB datatypes can be mapped to an Omnidex STRING or CLOB datatype. Omnidex does not support binary large objects.
The following table correlates the Oracle and Omnidex datatypes:
| Oracle Datatype | Omnidex Datatype | Comments |
|---|---|---|
| CHAR | CHAR(ACTER) | |
| VARCHAR2 | STRING or VARCHAR | Favor STRING unless your data cannot use a NULL terminator character. |
| NCHAR | NATIONAL CHAR(ACTER) | Omnidex has limited support for Unicode datatpes, but recommends the use of CHARACTER datatype. |
| NVARCHAR2 | NATIONAL VARCHAR | Omnidex has limited support for Unicode datatpes, but recommends the use of STRING datatype. |
| NUMBER | TINYINT, SMALLINT, INTEGER, BIGINT, FLOAT, DOUBLE | Favor the smallest Omnidex datatype that will accomodate the values in your data. |
| BINARY_FLOAT | FLOAT | |
| BINARY_DOUBLE | DOUBLE | |
| INTEGER | INTEGER | |
| SMALLINT | SMALLINT | |
| DATE | ORACLE DATETIME | |
| TIMESTAMP | ORACLE DATETIME | |
| CLOB | STRING or CLOB | Favor STRING unless your data cannot use a NULL terminator character. |
| NCLOB | STRING or NATIONAL CLOB | Omnidex has limited support for Unicode datatpes, but recommends the use of STRING datatype. |
| BFILE | Unsupported | |
| BLOB | Unsupported | |
| LONG | Unsupported | |
| RAW | Unsupported | |
| LONG RAW | Unsupported | |
| ROWID | ORACLE ROWID |
See also: