This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
integration:rdbms:odbc:datatypes [2011/04/07 17:41] doc |
integration:rdbms:odbc:datatypes [2011/04/15 21:05] deb |
||
|---|---|---|---|
| Line 21: | Line 21: | ||
| ==== Datatypes ==== | ==== Datatypes ==== | ||
| - | Omnidex supports most ODBC datatypes; however, care must be taken when mapping the ODBC datatypes to Omnidex. Omnidex accesses ODBC using the ODBC ODBC Connector, and so the datatype correlations will follow the ODBC standard. | + | 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. Omnidex can retrieve and return these datatypes, but cannot index beyond the standard ASCII character set. The ODBC NATIONAL datatypes should be declared as STRING or CHARACTER datatypes within 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 many of the ODBC LOB datatypes, though ODBC CLOB datatypes can be mapped to an Omnidex STRING or CLOB datatype. Omnidex does not support binary large objects. | + | Omnidex does not support binary large objects datatypes. |
| The following table correlates the ODBC and Omnidex datatypes: | The following table correlates the ODBC and Omnidex datatypes: | ||
| |< 100% 25% 25% 50% >| | |< 100% 25% 25% 50% >| | ||
| - | | ODBC Datatype | Omnidex Datatype | Comments | | + | ^ ODBC Datatype ^ Omnidex Datatype ^ Comments ^ |
| | SQL_CHAR | CHAR(ACTER) | | | | SQL_CHAR | CHAR(ACTER) | | | ||
| | SQL_VARCHAR | STRING or VARCHAR | Favor STRING unless your character data cannot be terminated by a NULL character. | | | 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_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 datatpes, but recommends the use of CHARACTER datatype. | | + | | 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 datatpes, but recommends the use of STRING 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 datatpes, 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_DECIMAL | DOUBLE, CHAR(ACTER) | | | ||
| | SQL_NUMERIC | DOUBLE, CHAR(ACTER) | | | | SQL_NUMERIC | DOUBLE, CHAR(ACTER) | | | ||