This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
integration:rdbms:sqlserver:datatypes [2011/04/08 04:11] doc |
integration:rdbms:sqlserver:datatypes [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 25: | Line 25: | ||
| 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 SQL Server 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. Omnidex can retrieve and return these datatypes, but cannot index beyond the standard ASCII character set. The SQL Server NATIONAL datatypes should be declared as STRING or CHARACTER datatypes within Omnidex. | ||
| - | Omnidex does not support many of the SQL Server LOB datatypes, though SQL Server CLOB datatypes can be mapped to an Omnidex STRING or CLOB datatype. Omnidex does not support binary large objects. | + | Omnidex does not support the SQL Server binary large object datatypes or the image datatypes. |
| The following table correlates the SQL Server and Omnidex datatypes: | The following table correlates the SQL Server and Omnidex datatypes: | ||
| Line 33: | Line 33: | ||
| | CHAR | CHAR(ACTER) | | | | CHAR | CHAR(ACTER) | | | ||
| | VARCHAR | STRING or VARCHAR | Favor STRING unless your character data cannot be terminated by a NULL character. | | | VARCHAR | 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. | |
| - | | NVARCHAR | NATIONAL VARCHAR | Omnidex has limited support for Unicode datatpes, but recommends the use of STRING datatype. | | + | | NVARCHAR | NATIONAL VARCHAR | Omnidex has limited support for Unicode datatypes, but recommends the use of STRING datatype. | |
| | BIT | TINYINT | | | | BIT | TINYINT | | | ||
| | TINYINT | TINYINT | | | | TINYINT | TINYINT | | | ||
| Line 48: | Line 48: | ||
| | SMALLDATETIME | ODBC DATETIME | | | | SMALLDATETIME | ODBC DATETIME | | | ||
| | DATETIME | ODBC DATETIME | | | | DATETIME | ODBC DATETIME | | | ||
| - | | DATETIMEOFFSET | ODBC DATETIME | | + | | DATETIMEOFFSET | ODBC DATETIME | | |
| - | | DATETIME2 | ODBC DATETIME | | + | | DATETIME2 | ODBC DATETIME | | |
| | TEXT | STRING or CLOB | Favor STRING unless your character data cannot be terminated by a NULL character. | | | TEXT | STRING or CLOB | Favor STRING unless your character data cannot be terminated by a NULL character. | | ||
| | BINARY | Unsupported | | | | BINARY | Unsupported | | | ||