README

A powerful Laravel package to detect and fix schema drift between your actual database and your migration files.

Why is this useful?

In a perfect world, your database schema exactly matches your migrations. In reality, "drift" happens:

• Developers manually add indexes or columns to the database for debugging or optimization and forget to create a migration.
• Merged branches might conflict in ways that migrations run but result in unexpected states.
• Legacy databases might have extra tables or columns not tracked in Laravel.

Laravel Migration Drift solves this by:

1. Introspecting your live database schema.
2. Simulating your migrations in a completely isolated in-memory SQLite database to determine the "perfect" expected state.
3. Comparing the two to find missing tables, extra columns, type mismatches, and index differences.
4. Generating SQL to fix the drift automatically.

Support for Multiple Connections

Yes! This package supports multiple database connections.

If you have multiple connections defined in your config/database.php (e.g., mysql, pgsql, tenant), you can specify which connection to check using the --database option.

Usage

Check for drift:

# Check default connection
php artisan migration:check-drift

# Check specific connection
php artisan migration:check-drift --database=tenant

# Generate a report file
php artisan migration:check-drift --report
php artisan migration:check-drift --report --report-format=html

Fix drift:

# Preview fixes for default connection
php artisan migration:fix-drift --dry-run

# Fix specific connection
php artisan migration:fix-drift --database=tenant

Features

• Drift Detection: Finds missing tables, extra columns, and modified types.
• Reporting: Generates reports in Markdown, HTML, or JSON formats.
• Strict Mode: Optional strict comparison for precise type matching.
• CI/CD Ready: Returns exit code 1 if drift is detected, making it perfect for CI pipelines.
• Auto-Fix: Generates ALTER TABLE and CREATE TABLE statements to sync your DB.
• Safe: Fixes require confirmation (unless --force is used) and won't drop data/tables automatically without clear comments.

Extra Tables (Safety First)

If your database has tables that are not in your migrations (e.g. legacy tables, analytics, etc.), this package will:

1. Report them as "Extra Tables" in the check command.
2. Ignore them intentionally when generating fixes. It will NEVER automatically generate DROP TABLE statements for them.
3. Instead, it will output a commented-out SQL suggestion (e.g., -- DROP TABLE analytics;) so you can manually run it if you really intended to delete it.

You can also explicitly ignore known extra tables using the --ignore-tables option:

php artisan migration:check-drift --ignore-tables=analytics,legacy_data

Installation

composer require kz370/laravel-migration-drift