This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
integration:rawdata:ost:environments [2011/04/08 16:09] deb |
integration:rawdata:ost:environments [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| {{page>:top_add&nofooter&noeditbtn}} | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | ====== Adminstration: Raw Data Files ====== | + | ====== Integration: Raw Data Files ====== |
| ===== Omnidex Standalone Tables ===== | ===== Omnidex Standalone Tables ===== | ||
| Line 41: | Line 41: | ||
| In the CREATE TABLE statement, the PHYSICAL clause is used to point to the physical location of the raw data file. This PHYSICAL clause can contain a relative path name (relative to the location of the Omnidex Environment File) such as "dat/states.ost", or an absolute path name such as "d:/class/lab1/dat/states.ost". Unlike fixed-length and delimited files, only one Omnidex Standalone Table can be referenced in the PHYSICAL clause, and wildcards are not allowed. The PHYSICAL clause can reference [[appendix:reference:envvar:home|environment variables]] using a special syntax. | In the CREATE TABLE statement, the PHYSICAL clause is used to point to the physical location of the raw data file. This PHYSICAL clause can contain a relative path name (relative to the location of the Omnidex Environment File) such as "dat/states.ost", or an absolute path name such as "d:/class/lab1/dat/states.ost". Unlike fixed-length and delimited files, only one Omnidex Standalone Table can be referenced in the PHYSICAL clause, and wildcards are not allowed. The PHYSICAL clause can reference [[appendix:reference:envvar:home|environment variables]] using a special syntax. | ||
| - | <code sql> | + | <code> |
| create table "STATES" | create table "STATES" | ||
| options "OST" | options "OST" | ||