## Filtering Options 

<field name="Name">Rafah</field> <field name="CountryCode">PSE</field> <field name="District">Rafah</field> <field name="Population">92020</field> </row> </table_data> </database> </mysqldump> 

The following options control which kinds of schema objects are written to the dump file: by category, such as triggers or events; by name, for example, choosing which databases and tables to dump; or even filtering rows from the table data using a WHERE  clause. 

## • --all-databases , -A 

Dump all tables in all databases. This is the same as using the --databases  option and naming all the databases on the command line. 

Note 

See the --add-drop-database  description for information about an incompatibility of that option with --all-databases . 

Prior to MySQL 8.0, the --routines  and --events  options for mysqldump  and mysqlpump  were not required to include stored routines and events when using the --all-databases  option: The dump included the mysql  system database, and therefore also the mysql.proc  and mysql.event  tables containing stored routine and event definitions. As of MySQL 8.0, the mysql.event  and mysql.proc tables are not used. Definitions for the corresponding objects are stored in data dictionary tables, but those tables are not dumped. To include stored routines and events in a dump made using --all- databases , use the --routines  and --events  options explicitly. 

## • --databases , -B 

Dump several databases. Normally, mysqldump  treats the first name argument on the command line as a database name and following names as table names. With this option, it treats all name arguments as database names. CREATE DATABASE  and USE  statements are included in the output before each new database. 

This option may be used to dump the performance_schema  database, which normally is not dumped even with the --all-databases  option. (Also use the --skip-lock-tables  option.) 

## • --events , -E 

Note 

See the --add-drop-database  description for information about an incompatibility of that option with --databases . 

Include Event Scheduler events for the dumped databases in the output. This option requires the EVENT privileges for those databases. 

The output generated by using --events  contains CREATE EVENT  statements to create the events. 

## • --ignore-error= error[,error]... 

