This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
integration:rdbms:odbc:datatypes [2011/04/07 17:44] doc |
integration:rdbms:odbc:datatypes [2011/04/15 21:05] deb |
||
---|---|---|---|
Line 34: | Line 34: | ||
| 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) | | |