nuodb-migrator schema

--source.driver=driver

Yes

nuodb-migrator dump only

JDBC driver class name

--source.url=url

Yes

nuodb-migrator dump only

Source database connection URL in the standard syntax: jdbc:subprotocol:subname

Optionally, include the source database username and password in the url specification. As shown in the following table, the syntax can vary according to the source database. The url examples show the specification of rootuser as the username and rootpw as the password.

It is allowed to specify the database username and password in both the source.url option and in the source.username and source.password options. If you do this and the specifications are not the same then there is a warning message but the nuodb-migrator schema command continues execution by using one of the specifications. Which specification the command uses depends on which source driver you are using:

--source.username= username

Yes

nuodb-migrator dump only

Source database username. Alternatively you can specify the user name in the source.url option.

--source.password= password

No

nuodb-migrator dump only

Source database password. Alternatively you can specify the password in the source.url option.

--source.properties= properties

No

nuodb-migrator dump only

Additional connection properties encoded as URL query string, e.g. “property1=value1&property2=value2…​”

--source.catalog=catalog

No

nuodb-migrator dump only

Default database catalog name to use

--source.schema=schema

No

nuodb-migrator dump only

Default database schema name to use

--source.auto.commit= { true | false }

No

nuodb-migrator dump only

If set to true, each individual statement is treated as a transaction and is automatically committed after it is executed. The default is false.

--source.transaction. isolation=value

No

nuodb-migrator dump only

Sets the transaction isolation level for the migration execution. A valid value can be either a symbolic name or an integer constant representing transaction isolation levels as defined in the JDBC java.sql.Connection class. Valid values include:

NuoDB does not support all of the levels, only read.committed or 2, serializable or 8 and two additional levels that are not in the JDBC standard. See Supported Transaction Isolation Levels for more information.

Option

Required?

schema option valid for nuodb-migrator dump and/or nuodb-migrator load command

Description

--target.url=url

No

nuodb-migrator load only

Target database connection URL in the format, jdbc:com.nuodb://host:port/database

--target.username= username

No

nuodb-migrator load only

Target database user name

--target.password= password

No

nuodb-migrator load only

Target database password

--target.properties= properties

No

nuodb-migrator load only

Additional connection properties encoded as URL query string, e.g. “property1=value1&property2=value2…​”

--target.schema=schema

No

nuodb-migrator load only

Database schema name to use. If not provided, objects will be generated in the same schema as the source database schema.

--output.path=path/filename

No

-

Saves DDL SQL script to a file specified by path/filename. If this parameter is omitted, the DDL is displayed to standard output.

--table.type=table_type[,table_type…​]

No

nuodb-migrator dump and/or nuodb-migrator load

Comma separated types of table objects (TABLE, SYSTEM TABLE, GLOBAL TEMPORARY, ALIAS, SYNONYM, etc. to process. By default, only TABLE type is processed. Views, triggers, functions, and stored procedures are not currently supported by the nuodb-migrator tool.

--meta.data.value={true | false}

No

nuodb-migrator dump and/or nuodb-migrator load

Includes or excludes specific metadata types from the generated output. Valid values are:

By default, all objects are generated. If you have tables with a sequence auto-generated column, you cannot use the --meta.data.sequence=false option when migrating those tables.

--script.type={drop | create}

No

nuodb-migrator load only

Type of DDL statement to be generated for each object.

Default is both DROP and CREATE statements for each object.

--group.scripts.by={table | meta.data}

No

nuodb-migrator load only

Group generated DDL scripts. Group by table is the default. CREATE/ALTER statements for the table and all indexes, foreign keys, etc. will be generated before it moves to the next table CREATE statement.

--identifier.quoting={ minimal | always | fully_qualified_class_name}

No

nuodb-migrator load only

Identifier quoting policy name, implementing com.nuodb.migrator.jdbc.dialect.IdentifierQuoting. Valid options are:

--identifier.normalizer={ noop | standard | lowercase | uppercase | fully_qualified_class_name }

No

nuodb-migrator load only

Identifier transform to use, implementing com.nuodb.migrator.jdbc.dialect.IdentifierNormalizer. Valid options are:

--naming.strategy={ auto | hash | qualify}

No

nuodb-migrator load only

Naming strategy to define how some object names are generated. This relates to objects of type index, foreign key, sequence, trigger. Valid options are:

--type.code=type_code

No

nuodb-migrator load only

This parameter identifies a type in the source database for which we want to specify a customized mapping. See type.code.

--type.size=type_size

No

nuodb-migrator load only

Defines the size of a source data type. This parameter will allow you to map source types of different sizes to different target types. See also type.size, precision, scale.

--type.precision=type_precision

No

nuodb-migrator load only

The maximum total number of decimal digits that can be stored, both to the left and to the right of the decimal point. This parameter will allow you to map source types of different precision to different target types. See also type.size, precision, scale.

--type.scale=type_scale

No

nuodb-migrator load only

The number of fractional digits (digits after the decimal point) for numeric data types. This parameter will allow you to map source types of different scale to different target types. See also type.size, precision, scale.

--type.name=type_name

No

nuodb-migrator load only

SQL type name , i.e., DECIMAL(p[,s]) or VARCHAR(n), where p is precision, s is scale, and n is a maximum size. See type.name.

--config=path

No

nuodb-migrator load only

Specifies a custom type mapping configuration file, where path is a full path and filename for the file. This file is used to transform source database data types to target database data types. If the file conf/nuodb-types.config is to be used, it is not necessary to use this parameter. It is only necessary to use the --use.nuodb.types=true command line parameter.

--use.nuodb.types={ true | false }

No

nuodb-migrator load only

Instructs nuodb-migrator to transform source database types to the best matching NuoDB types, where CHAR, VARCHAR and CLOB source types will be rendered as STRING columns. The conf/nuodb-types.config file is the source file for type overrides. If some other file is to be used, the --config=path parameter must be used to define the file. This option is false by default. See Example of nuodb-migrator Schema Command, and use.nuodb.types below.

--use.explicit.defaults={ true | false }

No

nuodb-migrator load only

Affects only MySQL implicit default values. This option allows MySQL implicit defaults to be moved over to the NuoDB schema explicitly. The option is false by default. See Example of nuodb-migrator Schema Command.