This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dev:odxsql:commands:extract:home [2010/07/04 18:27] tdo |
dev:odxsql:commands:extract:home [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| {{page>:top_add&nofooter&noeditbtn}} | {{page>:top_add&nofooter&noeditbtn}} | ||
| <html><div align="center"><span style="color:red">DRAFT</span></div></html> | <html><div align="center"><span style="color:red">DRAFT</span></div></html> | ||
| - | ====== Omnidex SQL: EXTRACT DDL ====== | + | ====== Omnidex SQL: EXTRACT (DDL and DML Statements) ====== |
| {{page>:sql_bar&nofooter&noeditbtn}} | {{page>:sql_bar&nofooter&noeditbtn}} | ||
| + | |||
| ===== Description ===== | ===== Description ===== | ||
| The OdxSQL EXTRACT command will Extract DDL statements (CREATE ENVIRONMENT, CREATE DATABASE, CREATE TABLE, CREATE INDEX and CREATE INDEX GROUP) from the currently connected Omnidex Environment to a file. The extracted file can then be modified with an editor and used to build another Omnidex Environment. | The OdxSQL EXTRACT command will Extract DDL statements (CREATE ENVIRONMENT, CREATE DATABASE, CREATE TABLE, CREATE INDEX and CREATE INDEX GROUP) from the currently connected Omnidex Environment to a file. The extracted file can then be modified with an editor and used to build another Omnidex Environment. | ||
| Line 24: | Line 25: | ||
| === FOR DATABASE database_name === | === FOR DATABASE database_name === | ||
| The FOR DATABASE clause can be used to extract the DDL for a specific database should the Omnidex Environment contain multiple databases. | The FOR DATABASE clause can be used to extract the DDL for a specific database should the Omnidex Environment contain multiple databases. | ||
| - | + | ==== DML Statement Clauses ==== | |
| - | ==== DML Clauses ==== | + | The INSERT, UPDATE and DELETE SQL Data Manipulation Language statements can be generated with the Extract command. |
| === CLUSTERED === | === CLUSTERED === | ||
| The CLUSTERED option requires tables to be one parent table and any number of linked children. | The CLUSTERED option requires tables to be one parent table and any number of linked children. | ||
| + | |||
| + | === DML Type (INSERTS | UPDATES | DELETE_WHERES | DELETE_EXCEPTS) === | ||
| + | The DML Type specifies which type of DML statement is to be generated. Note that on DELETE statements, there are two types. DELETE_WHERE and DELETE_EXCEPTS. | ||
| + | |||
| + | === FROM table_specs ==== | ||
| + | FROM table_specs is one or more tables to use to generate the DML statements. | ||
| + | |||
| ==== TO filespec ==== | ==== TO filespec ==== | ||
| Line 40: | Line 48: | ||
| extract ddl to myenv.sql with delete; | extract ddl to myenv.sql with delete; | ||
| ===== Examples ===== | ===== Examples ===== | ||
| + | Extract DDL CREATE statements from a connected Environment. | ||
| connect myenv.xml; | connect myenv.xml; | ||
| extract ddl to myenvnew.sql; | extract ddl to myenvnew.sql; | ||
| + | Extract DDL to default extract.sql file. The extract.sql file must not exist. | ||
| + | extract ddl; | ||
| + | Extract INSERT statements from a named table. | ||
| extract inserts from table1 to table1_inserts.sql; | extract inserts from table1 to table1_inserts.sql; | ||
| {{page>:bottom_add&nofooter&noeditbtn}} | {{page>:bottom_add&nofooter&noeditbtn}} | ||