laravel/framework · error · RuntimeException

This database driver does not support dropping foreign keys.

Error message

This database driver does not support dropping foreign keys.

What it means

Grammar::compileDropForeign() throws RuntimeException on the base; all four shipped grammars override it. It compiles an ALTER TABLE ... DROP FOREIGN KEY/CONSTRAINT command. Reaching the base means the active connection's SchemaGrammar is the unimplemented base class.

Solutions

Use a supported driver (sqlite/mysql/pgsql/sqlsrv) for foreign-key migrations.
Override compileDropForeign(Blueprint, Fluent) in your custom grammar.
Issue the engine's native ALTER TABLE ... DROP CONSTRAINT/FOREIGN KEY via DB::statement.

Example fix

// before - throws on base grammar
Schema::table('orders', function (Blueprint $t) {
    $t->dropForeign('orders_user_id_foreign');
});

// after - raw DDL for the unsupported engine
DB::connection('custom')->statement('ALTER TABLE orders DROP CONSTRAINT orders_user_id_foreign');

Defensive patterns

Strategy: type-guard

Validate before calling

$grammar = Schema::getConnection()->getSchemaGrammar();
if (get_class($grammar) === \Illuminate\Database\Schema\Grammars\Grammar::class) {
    throw new \DomainException('Connection uses the base Grammar; cannot drop foreign keys.');
}

Type guard

function supportsCompileDropForeign(\Illuminate\Database\Schema\Grammars\Grammar $grammar): bool
{
    return (new \ReflectionMethod($grammar, 'compileDropForeign'))
        ->getDeclaringClass()->getName() !== \Illuminate\Database\Schema\Grammars\Grammar::class;
}

Try / catch

try {
    Schema::table('orders', fn ($t) => $t->dropForeign('orders_user_id_foreign'));
} catch (\RuntimeException $e) {
    if (str_contains($e->getMessage(), 'dropping foreign keys')) {
        DB::statement('ALTER TABLE orders DROP CONSTRAINT orders_user_id_foreign');
    } else {
        throw $e;
    }
}

Prevention

Never bind the base Grammar on a connection that runs migrations.
Implement compileDropForeign in custom grammars.
Smoke-test FK migrations on the actual target engine in CI.

When it happens

Trigger: Calling $table->dropForeign(...) in a migration on a connection whose SchemaGrammar is the base Grammar (custom driver). Also reached from Schema::dropForeign-style helper paths.

Common situations: Custom/community driver whose grammar never implemented dropForeign; test wiring that injects a base Grammar.

Related errors

AI-assisted analysis of laravel/framework@e0f6eb3518 (2026-08-11). Data as JSON: /api/errors/f7e12ddd018387f6. Report an issue: GitHub.

Appendix: source

Thrown at src/Illuminate/Database/Schema/Grammars/Grammar.php:294

        if (! is_null($command->onUpdate)) {
            $sql .= " on update {$command->onUpdate}";
        }

        return $sql;
    }

    /**
     * Compile a drop foreign key command.
     *
     * @param  \Illuminate\Database\Schema\Blueprint  $blueprint
     * @param  \Illuminate\Support\Fluent  $command
     * @return string
     *
     * @throws \RuntimeException
     */
    public function compileDropForeign(Blueprint $blueprint, Fluent $command)
    {
        throw new RuntimeException('This database driver does not support dropping foreign keys.');
    }

    /**
     * Compile the blueprint's added column definitions.
     *
     * @param  \Illuminate\Database\Schema\Blueprint  $blueprint
     * @return array
     */
    protected function getColumns(Blueprint $blueprint)
    {
        $columns = [];

        foreach ($blueprint->getAddedColumns() as $column) {
            $columns[] = $this->getColumn($blueprint, $column);
        }

        return $columns;
    }

View on GitHub (pinned to e0f6eb3518)