mysqldump is also very useful for populating databases by copying data from one
MySQL server to another:

    shell> mysqldump --opt db_name | mysql --host=remote_host -C db_name

It is possible to dump several databases with one command:

    shell> mysqldump --databases db_name1 [db_name2 ...] > my_databases.sql

To dump all databases, use the --all-databases option:

    shell> mysqldump --all-databases > all_databases.sql

For InnoDB tables, mysqldump provides a way of making an online backup:

    shell> mysqldump --all-databases --single-transaction > all_databases.sql

This backup acquires a global read lock on all tables (using FLUSH TABLES WITH READ
LOCK) at the beginning of the dump. As soon as this lock has been acquired, the
binary log coordinates are read and the lock is released. If long updating
statements are running when the FLUSH statement is issued, the MySQL server may get
stalled until those statements finish. After that, the dump becomes lock free and
does not disturb reads and writes on the tables. If the update statements that the
MySQL server receives are short (in terms of execution time), the initial lock
period should not be noticeable, even with many updates.

For point-in-time recovery (also known as �..roll-forward,�.. when you need to restore
an old backup and replay the changes that happened since that backup), it is often
useful to rotate the binary log (see Section 5.2.4, �..The Binary Log�..) or at least
know the binary log coordinates to which the dump corresponds:

    shell> mysqldump --all-databases --master-data=2 > all_databases.sql

Or:

    shell> mysqldump --all-databases --flush-logs --master-data=2
                  > all_databases.sql

The --master-data and --single-transaction options can be used simultaneously,
which provides a convenient way to make an online backup suitable for use prior to
point-in-time recovery if tables are stored using the InnoDB storage engine.

For more information on making backups, see Section 6.2, �..Database Backup Methods�..,
and Section 6.3, �..Example Backup and Recovery Strategy�...

If you encounter problems backing up views, please read the section that covers
restrictions on views which describes a workaround for backing up views when this
fails due to insufficient privileges. See Section E.4, �..Restrictions on Views�...

create  database if not exists bugs;

grant   select, insert,
        update, delete, index, alter, create, lock tables,
        create temporary tables, drop, references on bugs.*
to      bugs@localhost identified by 'admpasswd';

grant   select, insert,
        update, delete, index, alter, create, lock tables,
        create temporary tables, drop, references on bugs.*
to      bugs@'%' identified by 'admpasswd';

flush   privileges;

create  database if not exists phpgedview;

grant   select, insert,
        update, delete, index, alter, create, lock tables,
        create temporary tables, drop, references on phpgedview.*
to      ged@localhost identified by 'admpasswd';

grant   select, insert,
        update, delete, index, alter, create, lock tables,
        create temporary tables, drop, references on bugs.*
to      ged@'%' identified by 'admpasswd';

flush   privileges;

drop    database if exists ipplan;
create  database if not exists ipplan;

grant   select, insert,
        update, delete, index, alter, create, lock tables,
        create temporary tables, drop, references on ipplan.*
to      ipplan@localhost identified by 'admpasswd';

grant   select, insert,
        update, delete, index, alter, create, lock tables,
        create temporary tables, drop, references on bugs.*
to      ipplan@'%' identified by 'admpasswd';

flush   privileges;

#       this one is for the super-user/administrator

grant   all privileges on *.*
to      'username'@'localhost' identified by 'userpasswd' with grant option;

grant   all privileges on *.*
to      'username'@'%' identified by 'userpasswd' with grant option;

flush   privileges;

mysql --user=mysql --password='mysqlpassword' mysql < grant.sql