2020-04-03 13:23:32 +00:00
---
toc_priority: 42
toc_title: mysql
---
2020-03-20 10:10:48 +00:00
# mysql {#mysql}
2019-05-18 17:25:58 +00:00
2019-05-30 15:12:56 +00:00
Allows `SELECT` queries to be performed on data that is stored on a remote MySQL server.
2019-05-18 17:25:58 +00:00
2020-03-20 10:10:48 +00:00
``` sql
2019-05-18 17:25:58 +00:00
mysql('host:port', 'database', 'table', 'user', 'password'[, replace_query, 'on_duplicate_clause']);
```
**Parameters**
2020-03-21 04:11:51 +00:00
- `host:port` — MySQL server address.
2020-03-20 10:10:48 +00:00
2020-03-21 04:11:51 +00:00
- `database` — Remote database name.
2020-03-20 10:10:48 +00:00
2020-03-21 04:11:51 +00:00
- `table` — Remote table name.
2020-03-20 10:10:48 +00:00
2020-03-21 04:11:51 +00:00
- `user` — MySQL user.
2020-03-20 10:10:48 +00:00
2020-03-21 04:11:51 +00:00
- `password` — User password.
2020-03-20 10:10:48 +00:00
2020-03-21 04:11:51 +00:00
- `replace_query` — Flag that converts `INSERT INTO` queries to `REPLACE INTO` . If `replace_query=1` , the query is replaced.
2020-03-20 10:10:48 +00:00
2020-03-21 04:11:51 +00:00
- `on_duplicate_clause` — The `ON DUPLICATE KEY on_duplicate_clause` expression that is added to the `INSERT` query.
2019-05-18 17:25:58 +00:00
2020-03-21 04:11:51 +00:00
Example: `INSERT INTO t (c1,c2) VALUES ('a', 2) ON DUPLICATE KEY UPDATE c2 = c2 + 1` , where `on_duplicate_clause` is `UPDATE c2 = c2 + 1` . See the MySQL documentation to find which `on_duplicate_clause` you can use with the `ON DUPLICATE KEY` clause.
2019-05-18 17:25:58 +00:00
2020-03-21 04:11:51 +00:00
To specify `on_duplicate_clause` you need to pass `0` to the `replace_query` parameter. If you simultaneously pass `replace_query = 1` and `on_duplicate_clause` , ClickHouse generates an exception.
2019-05-18 17:25:58 +00:00
2020-03-20 10:10:48 +00:00
Simple `WHERE` clauses such as `=, !=, >, >=, <, <=` are currently executed on the MySQL server.
2019-05-18 17:25:58 +00:00
The rest of the conditions and the `LIMIT` sampling constraint are executed in ClickHouse only after the query to MySQL finishes.
**Returned Value**
A table object with the same columns as the original MySQL table.
2020-03-20 10:10:48 +00:00
## Usage Example {#usage-example}
2019-05-18 17:25:58 +00:00
Table in MySQL:
2020-03-20 10:10:48 +00:00
``` text
2019-05-18 17:25:58 +00:00
mysql> CREATE TABLE `test` .`test` (
-> `int_id` INT NOT NULL AUTO_INCREMENT,
-> `int_nullable` INT NULL DEFAULT NULL,
-> `float` FLOAT NOT NULL,
-> `float_nullable` FLOAT NULL DEFAULT NULL,
-> PRIMARY KEY (`int_id`));
Query OK, 0 rows affected (0,09 sec)
mysql> insert into test (`int_id`, `float` ) VALUES (1,2);
Query OK, 1 row affected (0,00 sec)
mysql> select * from test;
2020-04-03 13:23:32 +00:00
+------+----------+-----+----------+
2019-05-18 17:25:58 +00:00
| int_id | int_nullable | float | float_nullable |
2020-04-03 13:23:32 +00:00
+------+----------+-----+----------+
2019-05-18 17:25:58 +00:00
| 1 | NULL | 2 | NULL |
2020-04-03 13:23:32 +00:00
+------+----------+-----+----------+
2019-05-18 17:25:58 +00:00
1 row in set (0,00 sec)
```
2019-05-30 15:12:56 +00:00
Selecting data from ClickHouse:
2019-05-18 17:25:58 +00:00
2020-03-20 10:10:48 +00:00
``` sql
2019-05-18 17:25:58 +00:00
SELECT * FROM mysql('localhost:3306', 'test', 'test', 'bayonet', '123')
```
2020-03-20 10:10:48 +00:00
``` text
2019-05-18 17:25:58 +00:00
┌─int_id─┬─int_nullable─┬─float─┬─float_nullable─┐
│ 1 │ ᴺᵁᴸᴸ │ 2 │ ᴺᵁᴸᴸ │
└────────┴──────────────┴───────┴────────────────┘
```
2020-03-20 10:10:48 +00:00
## See Also {#see-also}
2019-05-18 17:25:58 +00:00
2020-04-30 18:19:18 +00:00
- [The ‘ MySQL’ table engine ](../../engines/table-engines/integrations/mysql.md )
- [Using MySQL as a source of external dictionary ](../../sql-reference/dictionaries/external-dictionaries/external-dicts-dict-sources.md#dicts-external_dicts_dict_sources-mysql )
2019-05-18 17:25:58 +00:00
2020-01-30 10:34:55 +00:00
[Original article ](https://clickhouse.tech/docs/en/query_language/table_functions/mysql/ ) <!--hide-->