Overview | Environments | Databases | Tables | Constraints | Datatypes | Queries | Updates | Example
Omnidex supports most ODBC datatypes; however, care must be taken when mapping the ODBC datatypes to Omnidex.
Omnidex has very limited support for Unicode datatypes, also known as National Character datatypes or Wide Character Set datatypes. Omnidex can retrieve and return these datatypes, but cannot index beyond the standard ASCII character set. The SQL_W datatpyes should be declared as STRING or CHARACTER datatypes within Omnidex.
Omnidex does not support binary large objects datatypes.
The following table correlates the ODBC and Omnidex datatypes:
| ODBC Datatype | Omnidex Datatype | Comments |
|---|---|---|
| SQL_CHAR | CHAR(ACTER) | |
| SQL_VARCHAR | STRING or VARCHAR | Favor STRING unless your character data cannot be terminated by a NULL character. |
| SQL_LONGVARCHAR | STRING or VARCHAR | Favor STRING unless your character data cannot be terminated by a NULL character. |
| SQL_WCHAR | NATIONAL CHAR(ACTER) | Omnidex has limited support for Unicode datatypes, but recommends the use of CHARACTER datatype. |
| SQL_WVARCHAR | NATIONAL VARCHAR | Omnidex has limited support for Unicode datatypes, but recommends the use of STRING datatype. |
| SQL_WLONGVARCHAR | NATIONAL VARCHAR | Omnidex has limited support for Unicode datatypes, but recommends the use of STRING datatype. |
| SQL_DECIMAL | DOUBLE, CHAR(ACTER) | |
| SQL_NUMERIC | DOUBLE, CHAR(ACTER) | |
| SQL_SMALLINT | SMALLINT | |
| SQL_INTEGER | INTEGER | |
| SQL_REAL | FLOAT | |
| SQL_FLOAT | FLOAT | |
| SQL_DOUBLE | DOUBLE | |
| SQL_BIT | TINYINT | |
| SQL_TINYINT | TINYINT | |
| SQL_BIGINT | BIGINT | |
| SQL_TYPE_DATE | ODBC DATE | |
| SQL_TYPE_TIME | ODBC TIME | |
| SQL_TYPE_TIMESTAMP | ODBC DATETIME | |
| SQL_TYPE_UTCDATETIME | ODBC DATETIME | |
| SQL_TYPE_UTCTIME | ODBC TIME | |
| SQL_INTERVAL Datatypes | INTEGER | |
| SQL_GUID | CHAR(ACTER) | |
| SQL_BINARY | Unsupported | |
| SQL_VARBINARY | Unsupported | |
| SQL_LONGVARBINARY | Unsupported |
See also: