MDBTools(1)MDBTools(1)NAME
mdb-schema - Generate schema creation DDL
SYNOPSIS
mdb-schema [options] database [backend]
DESCRIPTION
mdb-schema is a utility program distributed with MDB Tools.
It produces DDL (data definition language) output for the given database. This can be passed to another database to create a replica of the
original access table format.
OPTIONS -T <table>, --table <table>
Single table option. Create schema for this table only. Default is to export all tables.
-N namespace
Prefix identifiers with namespace.
--drop-table
Issue DROP TABLE statement.
--no-drop-table
Don't issue DROP TABLE statement. This is the default.
--not-null
Issue NOT NULL constraints. This is the default.
--no-not-null
Don't issue NOT NULL constraints.
--default-values
Issue DEFAULT values.
--no-default-values
Don't issue DEFAULT values. This is the default.
--not-empty
Issue CHECK <> '' constraints.
--no-not-empty
Don't issue CHECK <> '' constraints. This is the default.
--indexes
Export INDEXes. This is the default.
--no-indexes
Don't export INDEXes.
--relations
Export foreign keys constraints. This is the default.
--no-relations
Don't export foreign keys constraints.
backend
Specifies target DDL dialect. Supported values are access, sybase, oracle, postgres, and mysql. If not specified the generated DDL
will be in access format.
ENVIRONMENT
MDB_JET3_CHARSET
Defines the charset of the input JET3 (access 97) file. Default is CP1252. See iconv(1).
MDBICONV
Defines the output charset to use for the SQL file. Default is UTF-8. mdbtools must have been compiled with iconv.
MDBOPTS
semi-column separated list of options:
o use_index
o no_memo
o debug_like
o debug_write
o debug_usage
o debug_ole
o debug_row
o debug_props
o debug_all is a shortcut for all debug_* options
NOTES HISTORY
mdb-schema first appeared in MDB Tools 0.1.
SEE ALSO gmdb2(1)mdb-export(1)mdb-hexdump(1)mdb-prop(1)mdb-sql(1)mdb-ver(1)mdb-array(1)mdb-header(1)mdb-parsecsv(1)mdb-tables(1)AUTHORS
The mdb-schema utility was written by Brian Bruns and others.
BUGS
Relationships and other features may not be supported by all databases. Access datatypes are mapped to their closest counterparts in the
target backend. This may not always yield an exact fit.
0.7 13 July 2013 MDBTools(1)
Check Out this Related Man Page
CREATE FOREIGN TABLE(7) PostgreSQL 9.2.7 Documentation CREATE FOREIGN TABLE(7)NAME
CREATE_FOREIGN_TABLE - define a new foreign table
SYNOPSIS
CREATE FOREIGN TABLE [ IF NOT EXISTS ] table_name ( [
{ column_name data_type [ OPTIONS ( option 'value' [, ... ] ) ] [ NULL | NOT NULL ] }
[, ... ]
] )
SERVER server_name
[ OPTIONS ( option 'value' [, ... ] ) ]
DESCRIPTION
CREATE FOREIGN TABLE will create a new foreign table in the current database. The table will be owned by the user issuing the command.
If a schema name is given (for example, CREATE FOREIGN TABLE myschema.mytable ...) then the table is created in the specified schema.
Otherwise it is created in the current schema. The name of the foreign table must be distinct from the name of any other foreign table,
table, sequence, index, or view in the same schema.
CREATE FOREIGN TABLE also automatically creates a data type that represents the composite type corresponding to one row of the foreign
table. Therefore, foreign tables cannot have the same name as any existing data type in the same schema.
To be able to create a table, you must have USAGE privilege on all column types.
PARAMETERS
IF NOT EXISTS
Do not throw an error if a relation with the same name already exists. A notice is issued in this case. Note that there is no guarantee
that the existing relation is anything like the one that would have been created.
table_name
The name (optionally schema-qualified) of the table to be created.
column_name
The name of a column to be created in the new table.
data_type
The data type of the column. This can include array specifiers. For more information on the data types supported by PostgreSQL, refer
to Chapter 8, Data Types, in the documentation.
NOT NULL
The column is not allowed to contain null values.
NULL
The column is allowed to contain null values. This is the default.
This clause is only provided for compatibility with non-standard SQL databases. Its use is discouraged in new applications.
server_name
The name of an existing server for the foreign table.
OPTIONS ( option 'value' [, ...] )
Options to be associated with the new foreign table or one of its columns. The allowed option names and values are specific to each
foreign data wrapper and are validated using the foreign-data wrapper's validator function. Duplicate option names are not allowed
(although it's OK for a table option and a column option to have the same name).
EXAMPLES
Create foreign table films with film_server:
CREATE FOREIGN TABLE films (
code char(5) NOT NULL,
title varchar(40) NOT NULL,
did integer NOT NULL,
date_prod date,
kind varchar(10),
len interval hour to minute
)
SERVER film_server;
COMPATIBILITY
The CREATE FOREIGN TABLE command largely conforms to the SQL standard; however, much as with CREATE TABLE, NULL constraints and zero-column
foreign tables are permitted.
SEE ALSO
ALTER FOREIGN TABLE (ALTER_FOREIGN_TABLE(7)), DROP FOREIGN TABLE (DROP_FOREIGN_TABLE(7)), CREATE TABLE (CREATE_TABLE(7)), CREATE SERVER
(CREATE_SERVER(7))
PostgreSQL 9.2.7 2014-02-17 CREATE FOREIGN TABLE(7)