schema-diff

Declarative pure-SQL schema management for MySQL and MariaDB

Terraform-style, declarative Postgres schema migration. Agent friendly.

SQL-file schema migrations for ClickHouse: cluster-aware, both drivers, schema dump & diff, opt-in Keeper lock, offline validate + pre-commit hook. CLI, Python API, GitHub Action, Docker.

A C# model class and database schema comparison, SQL diff scripting library

Schema comparison and fixup toolkit for Oracle to OceanBase and OceanBase-to-OceanBase migrations.

用于两个mysql数据库/sql文件之间表结构对比的工具

Eliminates Drizzle migration conflicts in team environments. Bridges Drizzle ORM with Liquibase — auto-diff TypeScript schemas against a live database, generate SQL migrations with automatic rollbacks. PostgreSQL, MySQL, SQLite, SingleStore. Uses drizzle-kit's own diff engine for a familiar interactive experience.

Declarative Postgres schemas: diff the live database against your SQL files, with before/after migration blocks and a hash ledger.

Multi-tenant SQLite database manager for .NET - per-tenant isolation, migrations, backups

Compare two database schemas, create and manage migrations

Declarative PostgreSQL schema management that turns SQL files into replay-safe migrations, generated TypeScript types, Zod validators, and guarded sync. No Docker, no shadow database, no ORM schema layer.

Catch breaking OpenAPI/REST API changes in CI before they reach production

Code-first entity development without migrations

Schema-first SQLite migrations. Keep your schema in .sql files, diff it against a database, apply.

TwinBridge — capture, replay, and diff your APIs. Build and test offline against twins that learned from your real traffic.

Language-agnostic database migrations compiled into reusable, self-documenting executables.

Versionado semántico para datos – detecta y clasifica cambios en datasets automáticamente.

IntelliJ IDEA plugin for visualizing SQL migration history, comparing schema versions, validating migration files, and drafting new migrations

Detect breaking API changes before they reach production

Prisma db push for SQLAlchemy: push, diff and check PostgreSQL/TimescaleDB schema straight from your models (SQLAlchemy / SQLModel). Risk-classified, CI-ready, no migration files.