This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
integration:rawdata:delimited:environments [2011/04/07 21:11] deb |
integration:rawdata:delimited: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 ====== |
| ===== Delimited Files ===== | ===== Delimited Files ===== | ||
| 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.csv", or an absolute path name such as "d:/class/lab1/dat/states.csv". This PHYSICAL clause can also contain wildcards as described below, and can also reference [[appendix:reference:envvar:home|environment variables]] using 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.csv", or an absolute path name such as "d:/class/lab1/dat/states.csv". This PHYSICAL clause can also contain wildcards as described below, and can also reference [[appendix:reference:envvar:home|environment variables]] using special syntax. | ||
| - | <code sql> | + | <code> |
| create table "STATES" | create table "STATES" | ||
| options "DELIMITED COLUMN=',' RECORD='\r\n' QUOTES" | options "DELIMITED COLUMN=',' RECORD='\r\n' QUOTES" | ||
| Line 50: | Line 50: | ||
| In the example above, a single file was used as the source of data for a table. It is also possible for multiple files to be used as the source of data for a table. As long as the files all share the same record layout, they will all be processed when reading the table. Filesets can be declared as a comma-separated list of files, or they can be declared using wildcards in the filename. In this example, three files are declared individually in the PHYSICAL clause: | In the example above, a single file was used as the source of data for a table. It is also possible for multiple files to be used as the source of data for a table. As long as the files all share the same record layout, they will all be processed when reading the table. Filesets can be declared as a comma-separated list of files, or they can be declared using wildcards in the filename. In this example, three files are declared individually in the PHYSICAL clause: | ||
| - | <code sql> | + | <code> |
| create table "STATES" | create table "STATES" | ||
| options "DELIMITED COLUMN=',' RECORD='\r\n' QUOTES" | options "DELIMITED COLUMN=',' RECORD='\r\n' QUOTES" | ||
| Line 61: | Line 61: | ||
| In this second example, wildcards are used to declare these files: | In this second example, wildcards are used to declare these files: | ||
| - | <code sql> | + | <code> |
| create table "STATES" | create table "STATES" | ||
| options "DELIMITED COLUMN=',' RECORD='\r\n' QUOTES" | options "DELIMITED COLUMN=',' RECORD='\r\n' QUOTES" | ||