Ansgar Becker

@MichaelMonashev if you say you get an SQL error, that means the connection itself was successfully, right? Further on, that means ClickHouse uses a protocol that's somehow compatible to MySQL/MariaDB,...

In that case I can probably add support for Clickhouse easily. I recently added support for ProxySQLAdmin for #350 as well, which also uses the MySQL protocol, but with a...

It's not possible to make all automatic queries optional. Some of them can be left away, but some others are required for editing table structure and data. There's just one...

You can help through testing for compatibility. As a starting point, I can add a new network type "Clickhouse MySQL", handling the `CONNECTION_ID()` query like in ProxySQL. You could already...

Next build has a "ClickHouse MySQL" network type:  And uses the system.metrics query. I guess we will hit more stuff to fix here.

Next queries I just tested using the ClickHouse playground: * `SELECT NOW()` -> works! * `SHOW VARIABLES` -> error: Syntax error: failed at position 6 ('VARIABLES') * `SHOW TABLES FROM...

Next build should at least open a connection without an error. Apart from that, Heidi will throw errors left and right due to the yet missing replacement for `SHOW TABLE...

Well I can check if [VirtualTreeview](https://github.com/Virtual-TreeView/Virtual-TreeView) supports such a selection. If not then I guess it's not solvable.

Is that in some way related to this issue?

* Is this sandboxing meant for _any_ application type, or is there some kind of recommendation for what type of application this is especially useful? (I'm just asking because HeidiSQL...