Skip to content

Commit 39c82f7

Browse files
Mazizovaclaude
andauthored
Software: add SQLGlot, MariaDB Shell for VS Code, TiProxy, vitess-operator (#172)
Claude-Session: https://claude.ai/code/session_011ngofGeLpoqVUnRtFVzEog Co-authored-by: Claude <[email protected]>
1 parent faa8b3c commit 39c82f7

6 files changed

Lines changed: 70 additions & 0 deletions

File tree

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
title: "MariaDB Shell for VS Code"
3+
link: "https://github.com/mariadb-corporation/vscode-extension"
4+
description: "The official MariaDB Corporation extension that brings MariaDB Shell into VS Code — a Connections view, SQL execution from .sql files with MariaDB-aware highlighting, an editable results grid, and GitHub Copilot integration through MariaDB Shell's MCP plugin."
5+
subcategories:
6+
- Database Management & GUI
7+
- AI & Ecosystem Skills
8+
compatibility:
9+
- MariaDB
10+
pricing:
11+
- Open Source
12+
images:
13+
- logo.png
14+
---
15+
16+
The extension drives a MariaDB Shell backend through its Model Context Protocol (MCP) plugin, exposing shell functions to the editor. It adds a Connections view for browsing servers, schemas, and database objects; SQL execution straight from `.sql` files with MariaDB-aware syntax highlighting; and an editable results grid, alongside REST Service and REST Daemon management and dump/load tasks.
17+
18+
It also integrates with GitHub Copilot, adding MariaDB-specific chat skills and an MCP server so Copilot can act on a connected MariaDB Shell session. It requires MariaDB Shell 26.10.3 or newer, with at least one connection configured via `mariadb-shell -- mcp setup` — the extension can install a suitable shell automatically if none is found. It's published by MariaDB Corporation under the GPLv2 license.
37.1 KB
Loading
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
title: "SQLGlot"
3+
link: "https://github.com/tobymao/sqlglot"
4+
description: "A no-dependency Python SQL parser, transpiler, optimizer, and query-building engine that converts SQL between 30+ dialects — including an officially maintained MySQL dialect — and can parse, format, analyze, and programmatically build SQL."
5+
subcategories:
6+
- Schema Management & Migration
7+
compatibility:
8+
- MySQL
9+
pricing:
10+
- Open Source
11+
images:
12+
- logo.png
13+
---
14+
15+
SQLGlot parses SQL into an expression tree that can be traversed, analyzed, and rebuilt programmatically, then regenerates it as valid SQL in any of its 30-plus supported target dialects — useful for migrating queries and DDL between database engines, or for building SQL programmatically without string concatenation. It also formats SQL and flags common syntax errors, such as unbalanced parentheses or misused reserved keywords.
16+
17+
MySQL is one of the dialects the core SQLGlot team maintains as "Official," meaning its bug fixes and feature additions get priority alongside dialects like PostgreSQL, BigQuery, Snowflake, and Trino. The project has no runtime dependencies, is written in Python, is released under the MIT license, and has around 9.7k stars on GitHub.
3.5 KB
Loading
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
title: "TiProxy"
3+
link: "https://github.com/pingcap/tiproxy"
4+
description: "A TiDB-native connection proxy built by PingCAP that keeps client connections alive across TiDB server upgrades, restarts, and scaling events, while load-balancing traffic and health-checking TiDB backends."
5+
subcategories:
6+
- Proxies & Traffic Management
7+
compatibility:
8+
- TiDB
9+
deployment:
10+
- Kubernetes
11+
- Self-Hosted
12+
pricing:
13+
- Open Source
14+
---
15+
16+
TiProxy sits in front of a TiDB cluster and migrates a backend instance's client connections to other TiDB instances when that instance restarts, shuts down, or is removed during a scale-in, so connections survive maintenance operations instead of being dropped. It also balances load across TiDB backends and runs health checks on them. In the project's local deployment example, clients connect to TiProxy through the standard `mysql` command-line client, the same way they would connect to TiDB directly.
17+
18+
It's deployed alongside TiUP or TiDB Operator, developed by the PingCAP organization under the Apache 2.0 license, and was forked from the Weir proxy project.
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
title: "vitess-operator"
3+
link: "https://github.com/planetscale/vitess-operator"
4+
description: "The Kubernetes operator for Vitess, maintained by PlanetScale — a VitessCluster custom resource that deploys and manages Vitess clusters on Kubernetes, with quickstart guides for AWS and GCP."
5+
subcategories:
6+
- DevOps & Deployment
7+
compatibility:
8+
- Vitess
9+
deployment:
10+
- Kubernetes
11+
pricing:
12+
- Open Source
13+
---
14+
15+
vitess-operator introduces a VitessCluster custom resource definition that lets Kubernetes manage the full lifecycle of a Vitess deployment — provisioning keyspaces, shards, and tablets, running scheduled vtbackup jobs, and tracking metrics — instead of configuring Vitess components by hand. The project documents quickstarts for both AWS and GCP, alongside a general Kubernetes setup guide and a VitessCluster API reference.
16+
17+
Maintained by PlanetScale under the Apache 2.0 license, its documentation includes a compatibility matrix pairing operator releases with supported Vitess and Kubernetes versions.

0 commit comments

Comments
 (0)