Case Analysis of replication usage of mysql Worm

This article introduces the relevant knowledge of "mysql worm replication case analysis". Many people will encounter such a dilemma in the operation of actual cases, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

Description

1. Migrate data from one table to another, or part of the specified data to another table.

2. Copy a large amount of data from one table to another.

3. Copy the data from a table to your own table to produce a large amount of data.

Example

Mysql > desc test +-+ | Field | Type | Null | Key | Default | Extra | +-+- -+ | id | int (11) | NO | PRI | NULL | auto_increment | | name | varchar (20) | YES | | NULL | | sex | varchar (1) | YES | | NULL | | | age | tinyint (3) unsigned | YES | | NULL | | +-+ mysql > desc user | +-+ | Field | Type | Null | Key | Default | Extra | +-+- -+ | id | int (11) | NO | PRI | NULL | auto_increment | | name | varchar (20) | YES | | NULL | | age | tinyint (3) unsigned | YES | | NULL | | | +-+-+ mysql > select * from test +-+ | id | name | sex | age | +-+ | 1 | name1 | male | 5 | 2 | name2 | female | 10 | 3 | name3 | male | 15 | 4 | name4 | male | 20 | +-+-+ -+-+ mysql > select * from user Empty set (0.00 sec) mysql > insert into user (name, age) select name, age from test;Query OK, 4 rows affected (0.00 sec) mysql > select * from user +-1 | name1 | 5 | 2 | name2 | 10 | 3 | name3 | 15 | 4 | name4 | 20 | +-+ "mysql worm replication usage instance analysis" ends here, thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!