Oracle 5.0 Reference Manual page 321

the same moment, you should use
[301] or
tables --master-data
•
--flush-privileges
Send a
FLUSH PRIVILEGES
option should be used any time the dump contains the
depends on the data in the
5.0.26.
• [301],
--force -f
Continue even if an SQL error occurs during a table dump.
One use for this option is to cause
view that has become invalid because the definition refers to a table that has been dropped. Without
[301],
--force 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
Dump data from the MySQL server on the given host. The default host is localhost.
• [301]
--hex-blob
Dump binary columns using hexadecimal notation (for example,
The affected data types are BINARY, VARBINARY, and the
columns are affected as well.
•
--ignore-table=db_name.tbl_name
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
Write
INSERT IGNORE
•
--lines-terminated-by=...
This option is used with the
clause for
LINES LOAD DATA
•
--lock-all-tables
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
[301].
lock-tables
• [301],
--lock-tables
For each dumped database, lock all tables to be dumped before dumping them. The tables are
locked with
READ LOCAL
tables such as
InnoDB
[301]
lock-tables
Because
--lock-tables
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
— A Database Backup Program
mysqldump
--flush-logs
[302].
[301]
statement to the server after dumping the
database for proper restoration. This option was added in MySQL
mysql
mysqldump
exits with an error message. With
[301],
-h host_name
[301]
statements rather than
[301]
[305] option and has the same meaning as the corresponding
--tab
INFILE. See
[301],
-x
-l
to permit concurrent inserts in the case of
and BDB,
--single-transaction
because it does not need to lock the tables at all.
[301] locks tables for each database separately, this option does not
[301]
301
[300] together with either
database and any other database that
mysql
to continue executing even when it encounters a
--force
'abc'
types. As of MySQL 5.0.13,
BLOB
[301]
statements.
INSERT
Section 13.2.6, "LOAD DATA INFILE
--single-transaction
[304]
--lock-all-
database. This
mysql
[301],
mysqldump
becomes 0x616263).
Syntax".
[304] and
tables. For transactional
MyISAM
is a much better option than
BIT
--
--