This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
integration:rdbms:oracle:datatypes [2011/04/04 03:19] doc created |
integration:rdbms:oracle:datatypes [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 23: | Line 23: | ||
| Omnidex supports most Oracle datatypes; however, care must be taken when mapping the Oracle datatypes to Omnidex. | 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. | + | 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. |
| - | 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 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. | 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. | ||
| Line 31: | Line 31: | ||
| The following table correlates the Oracle and Omnidex datatypes: | The following table correlates the Oracle and Omnidex datatypes: | ||
| - | ^ Oracle Datatype ^ Omnidex Datatype ^ Comments | + | |< 100% 25% 25% 50% >| |
| + | ^ Oracle Datatype ^ Omnidex Datatype ^ Comments ^ | ||
| | CHAR | CHAR(ACTER) | | | | CHAR | CHAR(ACTER) | | | ||
| - | | VARCHAR2 | STRING or VARCHAR | Favor STRING unless your data cannot use a NULL terminator character. | | + | | 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 datatpes, but recommends the use of CHARACTER datatype. | | + | | 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 datatpes, but recommends the use of STRING 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 will accomodate the values in your data. | | + | | 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_FLOAT | FLOAT | | | ||
| | BINARY_DOUBLE | DOUBLE | | | | BINARY_DOUBLE | DOUBLE | | | ||
| Line 43: | Line 44: | ||
| | DATE | ORACLE DATETIME | | | | DATE | ORACLE DATETIME | | | ||
| | TIMESTAMP | ORACLE DATETIME | | | | TIMESTAMP | ORACLE DATETIME | | | ||
| - | | CLOB | STRING or CLOB | Favor STRING unless your data cannot use a NULL terminator character. | | + | | 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 datatpes, but recommends the use of STRING datatype. | | + | | NCLOB | STRING or NATIONAL CLOB | Omnidex has limited support for Unicode datatypes, but recommends the use of STRING datatype. | |
| | BFILE | Unsupported | | | | BFILE | Unsupported | | | ||
| | BLOB | Unsupported | | | | BLOB | Unsupported | | | ||
| Line 50: | Line 51: | ||
| | RAW | Unsupported | | | | RAW | Unsupported | | | ||
| | LONG RAW | Unsupported | | | | LONG RAW | Unsupported | | | ||
| - | | ROWID | ORACLE ROWID | | + | | ROWID | ORACLE ROWID | | |