If you’re a MySQL user trying ClickHouse, one thing which is likely to surprise – and annoy you – is the handling of Double Quotes. In MySQL, you can use both double quotes and single quotes to quote strings, and as an example, these two queries are equivalent:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | mysql> select * from performance_schema.global_variables where variable_name='max_connections'; +-----------------+----------------+ | VARIABLE_NAME | VARIABLE_VALUE | +-----------------+----------------+ | max_connections | 151 | +-----------------+----------------+ 1 row in set (0.01 sec) mysql> select * from performance_schema.global_variables where variable_name="max_connections"; +-----------------+----------------+ | VARIABLE_NAME | VARIABLE_VALUE | +-----------------+----------------+ | max_connections | 151 | +-----------------+----------------+ 1 row in set (0.00 sec) |
This means that many of us tend to use single quotes and double quotes interchangeably. This is not the case, however, in ClickHouse.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 | fe0df8467851 :) select value from system.settings where name='max_threads'; SELECT value FROM system.settings WHERE name = 'max_threads' ┌─value─┐ │ 1 │ └───────┘ 1 rows in set. Elapsed: 0.009 sec. fe0df8467851 :) select value from system.settings where name="max_threads"; SELECT value FROM system.settings WHERE name = max_threads Received exception from server (version 19.7.5): Code: 47. DB::Exception: Received from localhost:9000, 127.0.0.1. DB::Exception: Missing columns: 'max_threads' while processing query: 'SELECT value FROM system.settings WHERE name = max_threads', required columns: 'value' 'name' 'max_threads', source columns: 'description' 'changed' 'value' 'name'. 0 rows in set. Elapsed: 0.007 sec. |
ClickHouse only allows using single quotes to quote strings while double quotes are used to quote identifiers (if you want to use special characters in the column name or something).
It is worth noting that it is ClickHouse’s behavior, not MySQL’s, according to the SQL Standard. In fact, if you set MySQL to ANSI SQL compatibility you will get a similar error message:
1 2 3 4 5 | mysql> set sql_mode='ansi'; Query OK, 0 rows affected, 1 warning (0.00 sec) mysql> select * from performance_schema.global_variables where variable_name="max_connections"; ERROR 1054 (42S22): Unknown column 'max_connections' in 'where clause' |
Unfortunately, there is no similar option in ClickHouse to allow double quotes for string quoting, so you may need to make this change when converting your queries to ClickHouse.
At the end we must stick to their way if need to work with them 🙂