This shows you the differences between two versions of the page.
|
dev:appendix:reference:datatypes [2010/07/06 21:19] els |
dev:appendix:reference:datatypes [2016/06/28 22:38] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | <html><div align="center"><span style="color:red">DRAFT</span></div></html> | ||
| - | ====== Appendix ====== | ||
| - | |||
| - | [[dev:appendix:home|Appendix]] -> [[dev:appendix:reference:home|Reference]] -> **[[dev:appendix:reference:datatypes|Omnidex Datatypes]]** | ||
| - | |||
| - | ===== Omnidex Datatypes ===== | ||
| - | |||
| - | Omnidex supports a wide variety of datatypes, including standard ANSI datatypes, Omnidex-specific datatypes and RDBMS-specific datatypes. | ||
| - | |||
| - | ==== Standard Datatypes ==== | ||
| - | |||
| - | Omnidex supports the following standard datatypes: | ||
| - | |||
| - | ^ Datatype ^ Description ^ | ||
| - | | CHARACTER(//n//) | Space-filled character string of //n// characters | | ||
| - | | CHAR(//n//) | Synonym for CHARACTER(//n//) | | ||
| - | | C STRING(//n//) | Null-terminated character string of //n// characters | | ||
| - | | VARCHAR(//n//)* | String of max //n// characters, with length variable | | ||
| - | | CLOB(//n//)* | Character large object of max //n// characters, with length variable | | ||
| - | | [SIGNED] TINYINT | 1-byte, signed integer ( -128 to 127 ) | | ||
| - | | UNSIGNED TINYINT | 1-byte, unsigned integer ( 0 to 255 ) | | ||
| - | | [SIGNED] SMALLINT | 2-byte, signed integer ( -32768 to 32767 ) | | ||
| - | | UNSIGNED SMALLINT | 2-byte, unsigned integer ( 0 to 65535 ) | | ||
| - | | [SIGNED] INTEGER | 4-byte, signed integer ( 2147483648 to 2147483647 ) | | ||
| - | | UNSIGNED INTEGER | 4-byte, unsigned integer ( 0 to 4294967295 ) | | ||
| - | | [SIGNED] BIGINT | 8-byte, signed integer ( %%-2^63 to 2^63-1%% ) | | ||
| - | | UNSIGNED BIGINT | 8-byte, unsigned integer ( %%0 to 2^64-1%% ) | | ||
| - | | FLOAT | IEEE four-byte, single-precision floating point | | ||
| - | | DOUBLE | IEEE eight-byte, double-precision floating point | | ||
| - | | DATE | 10-byte ANSI date | | ||
| - | | TIME | 11-byte ANSI time | | ||
| - | | DATETIME | 24-byte ANSI datetime | | ||
| - | | ASCII DATE | 8-byte ASCII date ( YYYYMMDD ) | | ||
| - | | ASCII DATE(6) | 6-byte ASCII date ( YYMMDD ) | | ||
| - | | ODBC DATE | 6-byte ODBC proprietary date | | ||
| - | | ODBC TIME | 6-byte ODBC proprietary time | | ||
| - | | ODBC DATETIME | 6-byte ODBC proprietary datetime | | ||
| - | | ORACLE DATE | 7-byte Oracle proprietary date | | ||
| - | | ORACLE TIME | 7-byte Oracle proprietary time | | ||
| - | | ORACLE DATETIME | 7-byte Oracle proprietary datetime | | ||
| - | | OMNIDEX DATE(//n//) | Omnidex proprietary date supporting //n// digits of YYYYMMDD | | ||
| - | | OMNIDEX TIME(//n//) | Omnidex proprietary time supporting //n// digits of HHMMSSNN | | ||
| - | | OMNIDEX DATETIME(//n//) | Omnidex proprietary datetime supporting //n// digits of YYYYMMDDHHMMSSNN | | ||
| - | | * Omnidex recommends use of the CHARACTER and C STRING datatypes rather than VARCHAR and CLOB due to the requirement of a length variable. || | ||
| - | |||
| - | ==== National Character Datatypes ==== | ||
| - | |||
| - | Omnidex also provides partial support for National Character Datatypes (sometimes called | ||
| - | Unicode datatypes or wide characters). The Omnidex SQL Engine will process these | ||
| - | datatypes, but the Omnidex Indexing Engine will only index the lower 8 bits of these | ||
| - | datatypes. | ||
| - | |||
| - | ^ Datatype ^ Description ^ | ||
| - | | NATIONAL CHARACTER(//n//) | Space-filled character string of //n// characters | | ||
| - | | NATIONAL CHAR(//n//) | Synonym for CHARACTER(//n//) | | ||
| - | | NATIONAL C STRING(//n//) | Null-terminated character string of //n// characters | | ||
| - | | NATIONAL VARCHAR(//n//)* | String of max //n// characters, with length variable | | ||
| - | | NATIONAL CLOB(//n//)* | Character large object of max //n// characters, with length variable | | ||
| - | | * Omnidex recommends use of the NATIONAL CHARACTER and NATIONAL C STRING datatypes rather than NATIONAL VARCHAR and NATIONAL CLOB due to the requirement of a length variable. || | ||
| - | |||
| - | |||
| - | - [[dev:appendix:articles:home|Articles]] | ||
| - | - **[[dev:appendix:articles:rollups|Rollup Tables]]** - A discussion of Rollup Tables and their use in Omnidex applications | ||
| - | - **[[dev:appendix:articles:oracle|Using Omnidex on Oracle Databases]]** - A discussion of the Oracle-specific considerations when building an Omnidex application. | ||
| - | - **[[dev:appendix:articles:sqlserver|Using Omnidex on SQL Server Databases]]** - A discussion of the SQL Server-specific considerations when building an Omnidex application. | ||
| - | - **[[dev:appendix:articles:mysql|Using Omnidex on MySQL Databases]]** - A discussion of the MySQL-specific considerations when building an Omnidex application. | ||
| - | - **[[dev:appendix:articles:odbc|Using Omnidex on Generic ODBC Databases]]** - A discussion of the ODBC-specific considerations when building an Omnidex application. | ||
| - | - **[[dev:appendix:articles:rawdatafiles|Using Omnidex on Raw Data Files]]** - A discussion of using Omnidex on fixed-length raw data files. | ||
| - | - **[[dev:appendix:articles:delimitedfiles|Using Omnidex on Delimited Data Files]]** - A discussion of using Omnidex on delimited data files. | ||
| - | - [[dev:appendix:reference:home|Reference]] | ||
| - | - **[[dev:appendix:reference:datatypes|Omnidex Datatypes]]** - Omnidex datatypes and their correlations to relational database datatypes | ||
| - | - [[dev:appendix:examples:home|Examples]] | ||
| - | |||
| - | {{page>:bottom_add&nofooter&noeditbtn}} | ||