v0.117.0

The Database tab now opens ClickHouse, OpenSearch / Elasticsearch and Redis next to PostgreSQL and MySQL, all through the connection's SSH session. Results can be sorted and searched, and a connection's database and Kafka settings share one Services tab with one Open button.

Databases

• Sort and find in results. A click on a column header sorts the result grid (ascending, descending, back to the server's order; numbers as numbers, NULL last), and Ctrl+F keeps only the rows containing the text, with the matching cells marked. Both work on the rows already fetched - on a table's Data view the page shown - and CSV / JSON export what is shown.
• ClickHouse joins PostgreSQL and MySQL / MariaDB in the Database tab, over its HTTP interface (8123, 8443 with TLS) and through the connection's SSH session like the others. Databases with their size, tables, views and materialized views; Data in the table's ORDER BY key, Structure with the primary and sorting keys and the data-skipping indexes, the server's own DDL. Each query tab is a ClickHouse session, so SET and USE carry between runs; Stop kills the query on the server. Read-only tabs run every statement with readonly = 2, which ClickHouse enforces itself. A statement with its own FORMAT comes back as lines, and INSERT reports the rows written.
• OpenSearch and Elasticsearch (the Wazuh indexer too) as a Database engine, through the SSH session like the others. The tree lists indices with document counts and sizes, aliases and data streams; Data shows documents with their fields flattened into columns, Structure the mapping, DDL the index's settings, mappings and aliases. Query tabs take Kibana console requests (GET /logs/_search and its JSON body) and SQL in one script: hits, _cat output and SQL results come back as a grid (SQL paged through the cursor), everything else as pretty-printed JSON. Read-only tabs send only reading requests. A password with no username is sent as an Elasticsearch API key.
• Redis (Valkey and KeyDB too) as a Database engine, with a protocol client of its own (no new dependency). The tree lists the numbered databases and, in each, the keys grouped by prefix (user:*); Data shows each key's type, TTL, size and a preview of its value. Query tabs run one command per line with redis-cli quoting: hashes, CONFIG GET and scores come back as two columns, INFO as a table, SCAN with its next cursor. Stop breaks off a blocking command. Read-only tabs send only read commands; commands that would take the connection over (MONITOR, SUBSCRIBE) are refused. Passwords in AUTH, CONFIG SET requirepass and ACL SETUSER are hidden in the audit log.
• Services tab. The connection and folder editors hold the database and Kafka settings in one Services tab, and the connection header has one Open button for them: a click opens the default database (or Kafka on a host without one), its arrow lists every database and Kafka.
• Each database in Databases on this host has its own TLS setting.
• Output shown a line per row (pretty JSON, a ClickHouse FORMAT) keeps its indentation in the grid.