Oracle 5.0, Справочное руководство

Страница: 321 / 3232

mysqldump
— A Database Backup Program
301
the same moment, you should use
--flush-logs
[300] together with either
--lock-all-
tables
[301] or
--master-data
[302] .
•
--flush-privileges
[301]
Send a
FLUSH PRIVILEGES
statement to the server after dumping the
mysql
database. This
option should be used any time the dump contains the
mysql
database and any other database that
depends on the data in the
mysql
database for proper restoration. This option was added in MySQL
5.0.26.
•
--force
[301] ,
-f
Continue even if an SQL error occurs during a table dump.
One use for this option is to cause
mysqldump
to continue executing even when it encounters a
view that has become invalid because the definition refers to a table that has been dropped. Without
--force
[301] ,
mysqldump
exits with an error message. With
--force
[301] ,
mysqldump
prints the error message, but it also writes an SQL comment containing the view definition to the
dump output and continues executing.
•
--host=host_name
[301] ,
-h host_name
Dump data from the MySQL server on the given host. The default host is
localhost
.
•
--hex-blob
[301]
Dump binary columns using hexadecimal notation (for example,
'abc'
becomes
0x616263
).
The affected data types are
BINARY
,
VARBINARY
, and the
BLOB
types. As of MySQL 5.0.13,
BIT
columns are affected as well.
•
--ignore-table=db_name.tbl_name
[301]
Do not dump the given table, which must be specified using both the database and table names. To
ignore multiple tables, use this option multiple times. This option also can be used to ignore views.
•
--insert-ignore
[301]
Write
INSERT IGNORE
statements rather than
INSERT
statements.
•
--lines-terminated-by=...
[301]
This option is used with the
--tab
[305] option and has the same meaning as the corresponding
LINES
clause for
LOAD DATA INFILE
. See Section 13.2.6, “
LOAD DATA INFILE
Syntax” .
•
--lock-all-tables
[301] ,
-x
Lock all tables across all databases. This is achieved by acquiring a global read lock for the duration
of the whole dump. This option automatically turns off
--single-transaction
[304] and
--
lock-tables
[301] .
•
--lock-tables
[301] ,
-l
For each dumped database, lock all tables to be dumped before dumping them. The tables are
locked with
READ LOCAL
to permit concurrent inserts in the case of
MyISAM
tables. For transactional
tables such as
InnoDB
and
BDB
,
--single-transaction
[304] is a much better option than
--
lock-tables
[301] because it does not need to lock the tables at all.
Because
--lock-tables
[301] locks tables for each database separately, this option does not
guarantee that the tables in the dump file are logically consistent between databases. Tables in
different databases may be dumped in completely different states.
•
--log-error=file_name
[301]