content_image/871703.jpg content_image/871720.jpg content_image/871721.jpg content_image/871710.jpg content_image/871719.jpg content_image/871716.jpg
<img src='content_image/871703.jpg'>

The string passed to this option is used to separate column values. The default value is a tab character ( 	 ). 

• --help 

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

Display help text and exit. 

• --hex 

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

If this option is used, all binary values are output in hexadecimal format. 

• --ignore-extended-pk-updates 

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

When using --allow-pk-changes , columns which become part of a table’s primary key must not be updated while the backup is being taken; such columns should keep the same values from the time values are inserted into them until the rows containing the values are deleted. If ndb_restore encounters updates to these columns when restoring a backup, the restore fails. Because some applications may set values for all columns when updating a row, even when some column values are not changed, the backup may include log events appearing to update columns which are not in fact modified. In such cases you can set --ignore-extended-pk-updates  to 1 , forcing ndb_restore to ignore such updates. 

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

For more information, see the description of --allow-pk-changes . 

• --include-databases = db-list 

## Important 

When causing these updates to be ignored, the user is responsible for ensuring that there are no updates to the values of any columns that become part of the primary key. 

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

Comma-delimited list of one or more databases to restore. Often used together with --include- tables ; see the description of that option for further information and examples. 

