Differences

This shows you the differences between two versions of the page.

Link to this comparison view

integration:rawdata:ost:environments [2011/03/14 14:21]
127.0.0.1 external edit
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 25: Line 25:
 === Declaring Databases for Raw Data Files === === Declaring Databases for Raw Data Files ===
  
-Databases in Omnidex are of a particular type, such as Oracle, SQL Server, MySQL or ODBC.  A database that accesses raw data file has its own type: FILE.  All tables within this database must be raw data files, though they can be a mixture of the types of raw data files supported by Omnidex.  +Databases in Omnidex are of a particular type, such as Oracle, SQL Server, MySQLor ODBC.  A database that accesses raw data file has its own type: FILE.  All tables within this database must be raw data files, though they can be a mixture of the types of raw data files supported by Omnidex.  
  
 <code> <code>
Line 39: Line 39:
 Tables will point to a single Omnidex Standalone Table, and the file must match the record layout specified in the [[dev:sql:statements:create_table:home|CREATE TABLE]] statement.  In the [[dev:sql:statements:create_table:home|CREATE TABLE]] statement, the OST option in the [[integration:rawdata:ost:options|OPTIONS clause]] is used to identify this as an Omnidex Standalone Table. Tables will point to a single Omnidex Standalone Table, and the file must match the record layout specified in the [[dev:sql:statements:create_table:home|CREATE TABLE]] statement.  In the [[dev:sql:statements:create_table:home|CREATE TABLE]] statement, the OST option in the [[integration:rawdata:ost:options|OPTIONS clause]] is used to identify this as an Omnidex Standalone Table.
  
-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|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"
 
Back to top
integration/rawdata/ost/environments.1300112479.txt.gz ยท Last modified: 2016/06/28 22:38 (external edit)
 
 
chimeric.de = chi`s home Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0