什么是 MariaDB？

这项技能使 AI 代理能够与 MariaDB 进行深度交互，MariaDB 是全球最流行的开源关系型数据库之一。通过利用 Openclaw Skills，开发人员可以确保其代理使用正确的 utf8mb4 字符集和专为现代应用程序设计的高效索引策略生成模式优化的查询。

除了基本的 CRUD 操作外，该技能还提供有关复杂数据库功能的专家级指导。这包括用于历史数据跟踪的系统版本表管理、用于半结构化工作负载的复杂 JSON 数据类型处理，以及配置 Galera 集群以确保企业级 Openclaw Skills 实现的高可用性和可扩展性。

下载入口:https://github.com/openclaw/skills/tree/main/skills/ivangdavila/mariadb

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

MariaDB 应用场景

• 设计具有优化复合索引和 Unicode 支持的高性能数据库架构。
• 使用系统版本控制实现时间数据跟踪，用于审计和历史分析。
• 通过查询执行计划分析和线程池配置优化数据库性能。
• 使用 Galera 管理分布式数据库集群，以实现弹性且高可用的 Openclaw Skills 环境。
• 使用高级 JSON 函数和取消嵌套技术处理半结构化数据。

1. AI 代理识别项目环境中的特定 MariaDB 需求。
2. 它应用字符集最佳实践，确保使用 utf8mb4 以实现完整的 Unicode 和表情符号兼容性。
3. 该技能生成优化查询，利用窗口函数和 CTE 等高级功能进行复杂的数据检索。
4. 它使用复杂的锁定机制和存储引擎选择（例如 InnoDB 与 Aria）管理数据库状态和并发性。
5. 代理使用 EXPLAIN ANALYZE 进行诊断检查，以确保查询符合 Openclaw Skills 生态系统中的特定性能基准。

MariaDB 配置指南

要在 Openclaw Skills 中使用此 MariaDB 技能，请确保您的本地计算机或服务器上安装了 MariaDB 客户端二进制文件。

# 在 Debian/Ubuntu 上安装 MariaDB
sudo apt-get install mariadb-client

# 使用 Homebrew 在 macOS 上安装 MariaDB
brew install mariadb

# 验证安装
mariadb --version

确保您的连接字符串配置为使用 utf8mb4 字符集，并且如果您计划使用临时表或序列，则用户具有足够的 DDL 操作权限。

MariaDB 数据架构与分类体系

该技能根据高性能标准组织其数据库逻辑和元数据：

name: MariaDB
description: Write efficient MariaDB queries with proper indexing, temporal tables, and clustering.
metadata: {"clawdbot":{"emoji":"??","requires":{"bins":["mariadb"]},"os":["linux","darwin","win32"]}}

Character Set

• Always use utf8mb4 for tables and connections—full Unicode including emoji
• utf8mb4_unicode_ci for proper linguistic sorting, utf8mb4_bin for byte comparison
• Set connection charset: SET NAMES utf8mb4 or in connection string
• Collation mismatch in JOINs forces conversion—kills index usage

Indexing

• TEXT/BLOB columns need prefix length: INDEX (description(100))
• Composite index order matters—(a, b) serves WHERE a=? but not WHERE b=?
• Foreign keys auto-create index on child table—but verify with SHOW INDEX
• Covering indexes: include all SELECT columns to avoid table lookup

Sequences

• CREATE SEQUENCE seq_name for guaranteed unique IDs across tables
• NEXT VALUE FOR seq_name to get next—survives transaction rollback
• Better than auto-increment when you need ID before insert
• SETVAL(seq_name, n) to reset—useful for migrations

System Versioning (Temporal Tables)

• ALTER TABLE t ADD SYSTEM VERSIONING to track all historical changes
• FOR SYSTEM_TIME AS OF '2024-01-01 00:00:00' queries past state
• FOR SYSTEM_TIME BETWEEN start AND end for change history
• Invisible columns row_start and row_end store validity period

JSON Handling

• JSON_VALUE(col, '$.key') extracts scalar, returns NULL if not found
• JSON_QUERY(col, '$.obj') extracts object/array with quotes preserved
• JSON_TABLE() converts JSON array to rows—powerful for unnesting
• JSON_VALID() before insert if column isn't strictly typed

Galera Cluster

• All nodes writable—but same-row conflicts cause rollback
• wsrep_sync_wait = 1 before critical reads—ensures node is synced
• Keep transactions small—large transactions increase conflict probability
• wsrep_cluster_size should be odd number—avoids split-brain

Window Functions

• ROW_NUMBER() OVER (PARTITION BY x ORDER BY y) for ranking within groups
• LAG(col, 1) OVER (ORDER BY date) for previous row value
• SUM(amount) OVER (ORDER BY date ROWS UNBOUNDED PRECEDING) for running total
• CTEs with WITH cte AS (...) for readable complex queries

Thread Pool

• Enable with thread_handling=pool-of-threads—better than thread-per-connection
• thread_pool_size = CPU cores for CPU-bound, higher for I/O-bound
• Reduces context switching with many concurrent connections
• Monitor with SHOW STATUS LIKE 'Threadpool%'

Storage Engines

• InnoDB default—ACID transactions, row locking, crash recovery
• Aria for temporary tables—crash-safe replacement for MyISAM
• MEMORY for caches—data lost on restart, but fast
• Check engine: SHOW TABLE STATUS WHERE Name='table'

Locking

• SELECT ... FOR UPDATE locks rows until commit
• LOCK TABLES t WRITE for DDL-like exclusive access—blocks all other sessions
• Deadlock detection automatic—one transaction rolled back; must retry
• innodb_lock_wait_timeout default 50s—lower for interactive apps

Query Optimization

• EXPLAIN ANALYZE for actual execution times (10.1+)
• optimizer_trace for deep dive: SET optimizer_trace='enabled=on'
• FORCE INDEX (idx) when optimizer chooses wrong index
• STRAIGHT_JOIN to force join order—last resort

Backup and Recovery

• mariadb-dump --single-transaction for consistent backup without locks
• mariadb-backup for hot InnoDB backup—incremental supported
• Binary logs for point-in-time recovery: mysqlbinlog binlog.000001 | mariadb
• Test restores regularly—backups that can't restore aren't backups

Common Errors

• "Too many connections"—increase max_connections or use connection pool
• "Lock wait timeout exceeded"—find blocking query with SHOW ENGINE INNODB STATUS
• "Row size too large"—TEXT/BLOB stored off-page, but row pointers have limits
• "Duplicate entry for key"—check unique constraints, use ON DUPLICATE KEY UPDATE