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 the internal NUMBER datatype. This datatype cannot be returned to applications, and so applications must choose an appropriate external datatype for presentation. Omnidex allows NUMBER datatypes to be returned as BIGINT, INTEGER, SMALLINT, TINYINT, FLOAT or DOUBLE. Note that if the EXTRACT statement is used to generate CREATE TABLE statements, Omnidex will consider the declared scale and precision and guess at an appropriate matching binary datatype; however, administrators should review and validate these assignments. 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.
Omnidex has very limited support for Unicode datatypes, also known as National Character datatypes. Omnidex can retrieve and return these datatypes, but cannot index beyond the standard ASCII character set. The Oracle NATIONAL datatypes should be declared as STRING or CHARACTER datatypes within Omnidex.
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 character data cannot be terminated by a NULL character. |
| NCHAR | NATIONAL CHAR(ACTER) | Omnidex has limited support for Unicode datatypes, but recommends the use of CHARACTER datatype. |
| NVARCHAR2 | NATIONAL VARCHAR | Omnidex has limited support for Unicode datatypes, but recommends the use of STRING datatype. |
| NUMBER | TINYINT, SMALLINT, INTEGER, BIGINT, FLOAT, DOUBLE | Favor the smallest Omnidex datatype that accommodate the values in your data for best performance. |
| BINARY_FLOAT | FLOAT | |
| BINARY_DOUBLE | DOUBLE | |
| INTEGER | INTEGER | |
| SMALLINT | SMALLINT | |
| DATE | ORACLE DATETIME | |
| TIMESTAMP | ORACLE DATETIME | |
| CLOB | STRING or CLOB | Favor STRING unless your character data cannot be terminated by a NULL character. |
| NCLOB | STRING or NATIONAL CLOB | Omnidex has limited support for Unicode datatypes, but recommends the use of STRING datatype. |
| BFILE | Unsupported | |
| BLOB | Unsupported | |
| LONG | Unsupported | |
| RAW | Unsupported | |
| LONG RAW | Unsupported | |
| ROWID | ORACLE ROWID |
See also: