Enhanced MySQL compatibility #9336

meob · 2020-02-24T09:58:30Z

Use case
The basic idea is to increase the MySQL compatibility with wire protocol in order to have tools like phpMyAdmin, DBeaver, ... working easily on ClickHouse (reading data)

Describe the solution you'd like
ClickHouse MySQL wire protocol works fine with application (eg. PHP, Perl, ...) but has problems with MySQL tools since they use "custom" SQL commands that MySQL understand while ClickHouse gives problems.
We propose to add a flag that enhance MySQL compatibility.
The solution requires two approach:

Support more MySQL command
There are commands like "SET NAMES utf8", "SET autocommit=1", ... that have no meaning
and can simply do nothing in CH but reply OK if the flag is active
Create the "mysql" data dictionary database
This can be easly created in ClickHouse using VIEWs from SYSTEM

The goal is to reach a "read only" compatibility with MySQL.
Creating CH data structures or traslating DML language requires much more work
and is not needed.

Describe alternatives you've considered
I used a simple self-made proxy to skip MySQL custom command... and it works!

Additional context
This compatibility could enable CH+wire protocol to be used as a MySQL DB with Linked Server in SQLServer, FDW in PostgreSQL, Oracle gateway, ...

I can provide the list of commands, variables, data dictionary views I have found till now...

alex-zaitsev · 2020-02-24T11:34:51Z

@meob , yes please add all incompatible commands that you have found so far. It will help a lot with implementation and testing.

One more requirement: compatibility mode should also support double quotes for strings, as MySQL does.

filimonov · 2020-02-24T11:58:26Z

One more requirement: compatibility mode should also support double quotes for strings, as MySQL does.

This one is very questionable, as MySQL behavior in that part is not standard and adjustable:
https://dev.mysql.com/doc/refman/8.0/en/sql-mode.html#sqlmode_ansi_quotes

alex-zaitsev · 2020-02-24T14:18:40Z

One more requirement: compatibility mode should also support double quotes for strings, as MySQL does.

This one is very questionable, as MySQL behavior in that part is not standard and adjustable:
https://dev.mysql.com/doc/refman/8.0/en/sql-mode.html#sqlmode_ansi_quotes

Yes, it is not standard, but it is default MySQL behaviour. If we want compatibility mode it makes sense to be compatible with defaults.

meob · 2020-02-26T08:51:22Z

I collected the SQL statements used by some tipical MySQL tools.
I used a legacy phpMyAdmin version since it is the easiest to hack.
Then the latest pgpMyAdmin version that is a bit more difficoult
to understand since it uses different threads connected to the database.
The latest one is DBeaver in which the first statement is performed
by the JDBC driver while the latter ones are performed by DBeaver itself.

phpMyAdmin 3.5.5 (Legacy)
SELECT @@Version, @@version_comment
SELECT * FROM information_schema.CHARACTER_SETS
SELECT * FROM information_schema.COLLATIONS
SHOW PLUGINS
SHOW DATABASES
SHOW TABLE STATUS FROM dd
SHOW TABLE STATUS FROM information_schema
SHOW TABLE STATUS FROM my2
SHOW TABLE STATUS FROM mysql
SHOW TABLE STATUS FROM performance_schema
SHOW TABLE STATUS FROM sys
... The same query for all MySQL databases
SELECT COUNT(*) FROM mysql.user
SHOW MASTER LOGS
SELECT USER()
SHOW GRANTS
SELECT 1 FROM information_schema.CHARACTER_SETS LIMIT 100000
SELECT 1 FROM information_schema.COLLATIONS LIMIT 100000
... The same query for all tables shown in the left menu

phpMyAdmin 5.0.1 (Latest version)
SELECT @@Version, @@version_comment
SET NAMES 'utf8mb4' COLLATE 'utf8mb4_general_ci'
SET lc_messages = 'en_US' SELECT CURRENT_USER()
SHOW GRANTS
SELECT SCHEMA_NAME FROM INFORMATION_SCHEMA.SCHEMATA
SELECT 1 FROM (SELECT GRANTEE, IS_GRANTABLE FROM INFORMATION_SCHEMA.COLUMN_PRIVILEGES UNION SELECT GRANTEE, IS_GRANTABLE FROM INFORMATION_SCHEMA.TABLE_PRIVILEGES UNION SELECT GRANTEE, IS_GRANTABLE FROM INFORMATION_SCHEMA.SCHEMA_PRIVILEGES UNION SELECT GRANTEE, IS_GRANTABLE FROM INFORMATION_SCHEMA.USER_PRIVILEGES) t WHERE IS_GRANTABLE = 'YES' AND '''meo''@''%''' LIKE GRANTEE LIMIT 1
SELECT 1 FROM INFORMATION_SCHEMA.USER_PRIVILEGES WHERE PRIVILEGE_TYPE = 'CREATE USER' AND '''meo''@''%''' LIKE GRANTEE LIMIT 1
SELECT 1 FROM mysql.user LIMIT 1
SELECT CHARACTER_SET_NAME AS Charset, DEFAULT_COLLATE_NAME AS Default collation, DESCRIPTION AS Description, MAXLEN AS Maxlen FROM information_schema.CHARACTER_SETS
SELECT COLLATION_NAME AS Collation, CHARACTER_SET_NAME AS Charset, ID AS Id, IS_DEFAULT AS Default, IS_COMPILED AS Compiled, SORTLEN AS Sortlen FROM information_schema.COLLATIONS
SHOW SESSION VARIABLES LIKE 'character_set_server'
SELECT USER()
SELECT SCHEMA_NAME FROM INFORMATION_SCHEMA.SCHEMATA, (SELECT DB_first_level FROM ( SELECT DISTINCT SUBSTRING_INDEX(SCHEMA_NAME, '', 1) DB_first_level FROM INFORMATION_SCHEMA.SCHEMATA WHERE TRUE ) t ORDER BY DB_first_level ASC LIMIT 0, 100) t2 WHERE TRUE AND 1 = LOCATE(CONCAT(DB_first_level, ''), CONCAT(SCHEMA_NAME, '')) ORDER BY SCHEMA_NAME ASC
SELECT COUNT(*) FROM ( SELECT DISTINCT SUBSTRING_INDEX(SCHEMA_NAME, '', 1) DB_first_level FROM INFORMATION_SCHEMA.SCHEMATA WHERE TRUE ) t
SHOW MASTER LOGS

DBeaver 6.3.5 (Latest version)
/* mysql-connector-java-5.1.46 ( Revision: 9cc87a48e75c2d2e87c1a293b2862ce651cb256e ) /SELECT @@session.auto_increment_increment AS auto_increment_increment, @@character_set_client AS character_set_client, @@character_set_connection AS character_set_connection, @@character_set_results AS character_set_results, @@character_set_server AS character_set_server, @@collation_server AS collation_server, @@init_connect AS init_connect, @@interactive_timeout AS interactive_timeout, @@license AS license, @@lower_case_table_names AS lower_case_table_names, @@max_allowed_packet AS max_allowed_packet, @@net_buffer_length AS net_buffer_length, @@net_write_timeout AS net_write_timeout, @@query_cache_size AS query_cache_size, @@query_cache_type AS query_cache_type, @@sql_mode AS sql_mode, @@system_time_zone AS system_time_zone, @@time_zone AS time_zone, @@transaction_isolation AS transaction_isolation, @@wait_timeout AS wait_timeout
SET NAMES utf8
SET character_set_results = NULL
SET autocommit=1
/ ApplicationName=DBeaver 6.3.5 - Main / SET autocommit=1
/ ApplicationName=DBeaver 6.3.5 - Main / SELECT DATABASE()
/ ApplicationName=DBeaver 6.3.5 - Metadata / SHOW ENGINES
/ ApplicationName=DBeaver 6.3.5 - Metadata / SHOW CHARSET
/ ApplicationName=DBeaver 6.3.5 - Metadata / SHOW COLLATION
/ ApplicationName=DBeaver 6.3.5 - Metadata / SELECT @@GLOBAL.character_set_server,@@GLOBAL.collation_server
/ ApplicationName=DBeaver 6.3.5 - Metadata / SHOW VARIABLES LIKE 'lower_case_table_names'
/ ApplicationName=DBeaver 6.3.5 - Metadata */ show databases

…-java setup for MySQL Handler ClickHouse#9336 mysql-connector setup query: /* mysql-connector-java-5.1.38 ( Revision: ${revinfo.commit} ) */SELECT @@session.auto_increment_increment AS auto_increment_increment, @@character_set_client AS character_set_client, @@character_set_connection AS character_set_connection, @@character_set_results AS character_set_results, @@character_set_server AS character_set_server, @@init_connect AS init_connect, @@interactive_timeout AS interactive_timeout... ClickHouse side Error: {} <Error> executeQuery: Code: 62, e.displayText() = DB::Exception: Syntax error: failed at position 74: @@session.auto_increment_increment AS auto_increment_increment, @@character_set_client AS character_set_client, @@character_set_connection AS character_set_conn. Expected one of: CAST, NULL... Client side Exception: java.sql.SQLException: Syntax error: failed at position 74: @@session.auto_increment_increment AS auto_increment_increment, @@character_set_client AS character_set_client, @@character_set_connection AS character_set_conn. Expected one of: CAST...

BohuTANG · 2020-04-03T08:34:18Z

Comments:

mysql-connector-java-5.1.34:
/* mysql-connector-java-5.1.34 ( Revision: jess.balint@oracle.com-20141014163213-wqbwpf1ok2kvo1om ) */SHOW VARIABLES WHERE Variable_name ='language' OR Variable_name = 'net_write_timeout' OR Variable_name = 'interactive_timeout' OR Variable_name = 'wait_timeout' OR Variable_name = 'character_set_client' OR Variable_name = 'character_set_connection' OR Variable_name = 'character_set' OR Variable_name = 'character_set_server' OR Variable_name = 'tx_isolation' OR Variable_name = 'transaction_isolation' OR Variable_name = 'character_set_results' OR Variable_name = 'timezone' OR Variable_name = 'time_zone' OR Variable_name = 'system_time_zone' OR Variable_name = 'lower_case_table_names' OR Variable_name = 'max_allowed_packet' OR Variable_name = 'net_buffer_length' OR Variable_name = 'sql_mode' OR Variable_name = 'query_cache_type' OR Variable_name = 'query_cache_size' OR Variable_name = 'license' OR Variable_name = 'init_connect' 2020.04.03 16:32:21.671607 [ 4101 ] {} <Error> executeQuery: Code: 62, e.displayText() = DB::Exception: Syntax error: failed at position 108: VARIABLES WHERE Variable_name ='language' OR Variable_name = 'net_write_timeout' OR Variable_name = 'interactive_timeout' OR Variable_name = 'wait_timeout' OR V. Expected one of: CREATE, GRANTS, QUOTA USAGE, QUOTAS, POLICIES, DICTIONARIES, TABLES, PROCESSLIST, CREATE, ROW POLICIES (version 20.4.1.1) (from 127.0.0.1:57474) (in query: /* mysql-connector-java-5.1.34 ( Revision: jess.balint@oracle.com-20141014163213-wqbwpf1ok2kvo1om ) */SHOW VARIABLES WHERE Variable_name ='language' OR Variable_name = 'net_write_timeout' OR Variable_name = 'interactive_timeout' OR Variable_name = 'wait_timeout' OR Variable_name = 'character_set_client' OR Variable_name = 'character_set_connection' OR Variable_name = 'character_set' OR Variable_name = 'character_set_server' OR Variable_name = 'tx_isolation' OR Variable_name = 'transaction_isolation' OR Variable_name = 'character_set_results' OR Variable_name = 'timezone' OR Variable_name = 'time_zone' OR Variable_name = 'system_time_zone' OR Variable_name = 'lower_case_table_names' OR Variable_name = 'max_allowed_packet' OR Variable_name = 'net_buffer_length' OR Variable_name = 'sql_mode' OR Variable_name = 'query_cache_type' OR Variable_name = 'query_cache_size' OR Variable_name = 'license' OR Variable_name = 'init_connect'

…se#9336

@variables

* Skip the `/* comments */ SELECT @@variables ...` from mysql-connector-java setup for MySQL Handler #9336 mysql-connector setup query: /* mysql-connector-java-5.1.38 ( Revision: ${revinfo.commit} ) */SELECT @@session.auto_increment_increment AS auto_increment_increment, @@character_set_client AS character_set_client, @@character_set_connection AS character_set_connection, @@character_set_results AS character_set_results, @@character_set_server AS character_set_server, @@init_connect AS init_connect, @@interactive_timeout AS interactive_timeout... ClickHouse side Error: {} <Error> executeQuery: Code: 62, e.displayText() = DB::Exception: Syntax error: failed at position 74: @@session.auto_increment_increment AS auto_increment_increment, @@character_set_client AS character_set_client, @@character_set_connection AS character_set_conn. Expected one of: CAST, NULL... Client side Exception: java.sql.SQLException: Syntax error: failed at position 74: @@session.auto_increment_increment AS auto_increment_increment, @@character_set_client AS character_set_client, @@character_set_connection AS character_set_conn. Expected one of: CAST... * add repalce 'SHOW VARIABLES' for mysql-connector-java-5.1.34 #9336 * Add java client(JDBC) integration test to test_mysql_protocol * shift out java tests from dbms * Update MySQLHandler.cpp * Update MySQLHandler.cpp * test_mysql_protocol: add Test.java exit code 1 when expection Co-authored-by: alexey-milovidov <milovidov@yandex-team.ru>

BohuTANG · 2020-04-13T01:08:55Z

Comments:

There are already 3 patches in place to address this compatibility issue:
[0] #10021
[1] #10140
[2] #10199

They addressed the SET commands:

SET NAMES ...
SET character_set_results ...
SET FOREIGN_KEY_CHECKS ...
SET AUTOCOMMIT ...
SET sql_mode ...
SET SESSION TRANSACTION ISOLATION LEVEL ...

These SET commands will return OK to the client/driver-side.

SELECT commands:

SELECT @@... (match this pattern)
/* ... */ SELECT @@... (match this pattern)
/* ... */ SHOW VARIABLES ... (match this pattern)

These SELECT commands will return max_allowed_packet by default.

meob · 2020-04-13T05:36:46Z

:)

BohuTANG · 2020-04-22T10:13:39Z

Comments:

workbench 8.0:

 SHOW SESSION VARIABLES LIKE 'lower_case_table_names'

2020.04.22 18:05:14.519488 [ 19356 ] {} <Error> executeQuery: Code: 62, e.displayText() = DB::Exception: Syntax error: failed at position 6: SESSION VARIABLES LIKE 'lower_case_table_names'. Expected one of: PROCESSLIST, CREATE, GRANTS, QUOTAS, QUOTA USAGE, POLICIES, ROW POLICIES, TABLES, DICTIONARIES, CREATE (version 20.4.1.1) (from 127.0.0.1:37774) (in query: SHOW SESSION VARIABLES LIKE 'lower_case_table_names'), Stack trace (when copying this message, always include the lines below):

BohuTANG · 2020-06-25T13:28:20Z

Comments:
Add select @@version #11815

BohuTANG · 2020-07-07T09:19:27Z

Comments:
Add KILL QUERY [connection_id] #12152

BohuTANG · 2020-07-10T06:32:23Z

Comments:
Add SELECT DATABASE() #12314

AlexeyMatskevich · 2020-09-03T03:07:59Z

I have the same problem for 20.7.2.30

Code: 62, e.displayText() = DB::Exception: Syntax error: failed at position 5 ('@@'): @@wait_timeout = 2147483. Expected one of: ROLE, identifier, ROLE DEFAULT, DEFAULT ROLE (version 20.7.2.30 (official build))

Is there any news about this?

BohuTANG · 2020-09-04T00:40:29Z

I have the same problem for 20.7.2.30

Code: 62, e.displayText() = DB::Exception: Syntax error: failed at position 5 ('@@'): @@wait_timeout = 2147483. Expected one of: ROLE, identifier, ROLE DEFAULT, DEFAULT ROLE (version 20.7.2.30 (official build))

Is there any news about this?

Not support SET @@var=x yet

BohuTANG · 2020-09-04T04:55:02Z

Comments:
Add SET @@var=x #14469

maqroll · 2020-09-23T17:34:37Z

Most prefab queries use just UNION. MySQL assumes DISTINCT by default. CK fails. Wouldn't be nice to have a setting to establish default behaviour of UNION to UNION ALL (and set it by default on mysql sessions)?

siradjev · 2020-12-25T20:19:22Z

.NET driver needs TIMEDIFF function:
Code: 46, e.displayText() = DB::Exception: Unknown function TIMEDIFF. Maybe you meant: ['dateDiff'] (version 20.8.9.6 (official build))

jploski · 2021-12-26T01:06:15Z

While trying to connect to Clickhouse using MySQL Workbench I ran into those:

show character set where charset = .*
SELECT current_user()
SHOW SESSION VARIABLES LIKE .*
SHOW SESSION STATUS LIKE .*
SET NAMES .*
SET CHARACTER SET .*
SELECT CONNECTION_ID()
SHOW FULL TABLES FROM .*
SHOW ENGINES
SHOW CHARSET
SHOW COLLATION

I was able to rewrite all of them using ProxySQL's mysql_query_rules.

But there is one which I cannot work around because it seems to be exempt from rewriting (sysown/proxysql#3736):

SET character_set_client=utf8;

Edit: I managed to work around it by hacking ProxySQL.

jbenguira · 2022-04-15T14:37:34Z

Any progress on this issue? It would really be lovely to have MySQL tooling working (workbench, PHPMyAdmin)

alexey-milovidov · 2022-12-18T09:33:42Z

@jbenguira Hi! There is no progress on this issue.

devicenull · 2023-01-19T17:50:14Z

We hit a similar issue with PowerBI - it tries to run this query:

SELECT @@max_allowed_packet, @@character_set_client, @@character_set_connection, @@license, @@sql_mode, @@lower_case_table_names, @@autocommit

When it first opens the connection, which results in clickhouse throwing:

DB::Exception: Syntax error: failed at position 6 ('COLLATION'): COLLATION. Expected one of: CREATE, FULL, DATABASES, CLUSTERS, FILESYSTEM CACHES, CLUSTER, CHANGED, SETTINGS, TABLES, DICTIONARIES, CREATE, PROCESSLIST, ACCESS, USERS, ROLES, SETTINGS PROFILES, PROFILES, ROW POLICIES, POLICIES, QUOTAS, CURRENT ROLES, ENABLED ROLES, CURRENT QUOTA, QUOTA, GRANTS, PRIVILEGES. (SYNTAX_ERROR) (version 22.12.3.5 (official build))

alexey-milovidov · 2023-01-23T21:02:40Z

@devicenull the query works:

milovidov@milovidov-desktop:~/work/ClickHouse/utils/changelog$ clickhouse-local 
ClickHouse local version 22.13.1.1.

milovidov-desktop :) SELECT @@max_allowed_packet, @@character_set_client, @@character_set_connection, @@license, @@sql_mode, @@lower_case_table_names, @@autocommit
                     

SELECT
    globalVariable('max_allowed_packet') AS `@@max_allowed_packet`,
    globalVariable('character_set_client') AS `@@character_set_client`,
    globalVariable('character_set_connection') AS `@@character_set_connection`,
    globalVariable('license') AS `@@license`,
    globalVariable('sql_mode') AS `@@sql_mode`,
    globalVariable('lower_case_table_names') AS `@@lower_case_table_names`,
    globalVariable('autocommit') AS `@@autocommit`

Query id: b4bb0656-5c95-4fec-8673-9810f2455629

┌─@@max_allowed_packet─┬─@@character_set_client─┬─@@character_set_connection─┬─@@license─┬─@@sql_mode─┬─@@lower_case_table_names─┬─@@autocommit─┐
│             67108864 │                      0 │                          0 │         0 │          0 │                        0 │            0 │
└──────────────────────┴────────────────────────┴────────────────────────────┴───────────┴────────────┴──────────────────────────┴──────────────┘

1 row in set. Elapsed: 0.002 sec.

devicenull · 2023-01-23T21:13:03Z

I agree, it works via clickhouse-client, but doesn't appear to work via the mysql port. Either way, we've moved to OBDC access for PowerBI, which is working fine.

LUAgam · 2023-07-04T05:34:47Z

Does jdbc's allowMultiQueries = true require support?

Basically `DATABASE()` and `SCHEMA()` are aliases in MySQL. This helps with allowing MySQL Shell to get one step closer to a functioning connection. To see what MySQL Shell does: ``` mysqlsh --verbose=4 --log-sql=unfiltered mysql://default@127.0.0.1:9004 ``` This might also bring other tools a step closer to working with the MySQL compatibility of ClickHouse. Ref: ClickHouse#9336 Signed-off-by: Daniël van Eeden <git@myname.nl>

meob added the feature label Feb 24, 2020

filimonov added the comp-foreign-db Integrations with other databases label Feb 24, 2020

filimonov mentioned this issue Mar 20, 2020

Add INFORMATION_SCHEMA database #9770

Closed

BohuTANG added a commit to BohuTANG/ClickHouse that referenced this issue Apr 3, 2020

add repalce 'SHOW VARIABLES' for mysql-connector-java-5.1.34 ClickHou…

96ec781

…se#9336

BohuTANG mentioned this issue Apr 5, 2020

Enhanced compatibility with native mysql-connector-java(JDBC) #10021

Merged

filimonov mentioned this issue Jul 8, 2020

superset connect to clickhouse via mysql protocol, report error #12283

Closed

BohuTANG mentioned this issue Jul 9, 2020

Support MySQL 'SELECT DATABASE()' #12314

Merged

filimonov added the comp-mysql label Jul 9, 2020

BohuTANG mentioned this issue Sep 4, 2020

Support MySQL handler 'set @@xx' settting #14469

Merged

filimonov mentioned this issue Nov 17, 2020

MySQL add support for SQL_SELECT_LIMIT (compatibility with datastudio) #17115

Closed

siradjev mentioned this issue Dec 29, 2020

Add support for TIMEDIFF function in MySQL Wire protocol (Mysql.Data .NET driver) #18612

Closed

alexey-milovidov mentioned this issue Sep 16, 2021

INFORMATION SCHEMA enhancement #29068

Open

jploski mentioned this issue Dec 26, 2021

Cannot suppress SET character_set_client=utf8? sysown/proxysql#3736

Open

FArthur-cmd mentioned this issue Jan 31, 2023

Add support for SHOW ENGINES query #45859

Merged

mshustov mentioned this issue Feb 15, 2023

MySQL compatibility: add support for SHOW COLUMNS, SHOW FULL TABLES #46437

Closed

dveeden mentioned this issue Aug 19, 2023

Improve MySQL Compatibility by supporting SCHEMA() #53587

Merged

1 task

bishrtabbaa mentioned this issue Mar 5, 2024

initial Athena Clickhouse connector commit related to issue 1754 awslabs/aws-athena-query-federation#1770

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Enhanced MySQL compatibility #9336

Enhanced MySQL compatibility #9336

meob commented Feb 24, 2020

alex-zaitsev commented Feb 24, 2020

filimonov commented Feb 24, 2020

alex-zaitsev commented Feb 24, 2020

meob commented Feb 26, 2020

BohuTANG commented Apr 3, 2020

BohuTANG commented Apr 13, 2020

meob commented Apr 13, 2020

BohuTANG commented Apr 22, 2020

BohuTANG commented Jun 25, 2020 •

edited

BohuTANG commented Jul 7, 2020

BohuTANG commented Jul 10, 2020

AlexeyMatskevich commented Sep 3, 2020

BohuTANG commented Sep 4, 2020

BohuTANG commented Sep 4, 2020 •

edited

maqroll commented Sep 23, 2020

siradjev commented Dec 25, 2020

jploski commented Dec 26, 2021 •

edited

jbenguira commented Apr 15, 2022

alexey-milovidov commented Dec 18, 2022

devicenull commented Jan 19, 2023

alexey-milovidov commented Jan 23, 2023

devicenull commented Jan 23, 2023

LUAgam commented Jul 4, 2023

Enhanced MySQL compatibility #9336

Enhanced MySQL compatibility #9336

Comments

meob commented Feb 24, 2020

alex-zaitsev commented Feb 24, 2020

filimonov commented Feb 24, 2020

alex-zaitsev commented Feb 24, 2020

meob commented Feb 26, 2020

BohuTANG commented Apr 3, 2020

BohuTANG commented Apr 13, 2020

meob commented Apr 13, 2020

BohuTANG commented Apr 22, 2020

BohuTANG commented Jun 25, 2020 • edited

BohuTANG commented Jul 7, 2020

BohuTANG commented Jul 10, 2020

AlexeyMatskevich commented Sep 3, 2020

BohuTANG commented Sep 4, 2020

BohuTANG commented Sep 4, 2020 • edited

maqroll commented Sep 23, 2020

siradjev commented Dec 25, 2020

jploski commented Dec 26, 2021 • edited

jbenguira commented Apr 15, 2022

alexey-milovidov commented Dec 18, 2022

devicenull commented Jan 19, 2023

alexey-milovidov commented Jan 23, 2023

devicenull commented Jan 23, 2023

LUAgam commented Jul 4, 2023

BohuTANG commented Jun 25, 2020 •

edited

BohuTANG commented Sep 4, 2020 •

edited

jploski commented Dec 26, 2021 •

edited