content_image/822598.jpg content_image/822597.jpg content_image/822596.jpg content_image/822595.jpg content_image/822594.jpg
MySQL replication; see Replication of Columns Having Different Data Types, for information about specific type conversions currently supported by attribute demotion. 

Beginning with NDB 8.0.26, this option also makes it possible to restore a NULL  column as NOT NULL . The column must not contain any NULL  entries; otherwise ndb_restore  stops with an error. 

ndb_restore  reports any truncation of data that it performs during lossy conversions once per attribute and column. 

• --no-binlog 

<img src='content_image/822598.jpg'>

This option prevents any connected SQL nodes from writing data restored by ndb_restore  to their binary logs. 

• --no-restore-disk-objects , -d 

<img src='content_image/822597.jpg'>

This option stops ndb_restore  from restoring any NDB Cluster Disk Data objects, such as tablespaces and log file groups; see Section 23.5.10, “NDB Cluster Disk Data Tables” , for more information about these. 

• --no-upgrade , -u 

<img src='content_image/822596.jpg'>

When using ndb_restore  to restore a backup, VARCHAR  columns created using the old fixed format are resized and recreated using the variable-width format now employed. This behavior can be overridden by specifying --no-upgrade . 

• --ndb-connectstring 

<img src='content_image/822595.jpg'>

Set connect string for connecting to ndb_mgmd. Syntax: "[nodeid=id;][host=]hostname[:port]". Overrides entries in NDB_CONNECTSTRING and my.cnf. 

• --ndb-mgmd-host 

<img src='content_image/822594.jpg'>

