laravel/framework · error · RuntimeException

This database driver does not support retrieving columns.

Error message

This database driver does not support retrieving columns.

What it means

Grammar::compileColumns() is a RuntimeException stub on the base class. All four shipped grammars override it, so reaching the base means an unimplemented/custom grammar. Builder::getColumns(), getColumnListing(), getColumnType(), hasColumn(), and the column paths of getIndexes() all route through here.

Solutions

Switch the connection to a supported driver (sqlite/mysql/pgsql/sqlsrv).
Implement compileColumns($schema, $table) in your custom grammar, returning the engine's column-listing SQL.
Query information_schema.columns directly as a temporary measure.

Example fix

// before - base grammar throws
$cols = Schema::connection('custom')->getColumns('users');

// after - implement in CustomGrammar, or query raw
$cols = DB::connection('custom')->select(
    "SELECT column_name, data_type FROM information_schema.columns WHERE table_name = ?",
    ['users']
);

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 list columns.');
}

Type guard

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

Try / catch

try {
    $cols = Schema::getColumns('users');
} catch (\RuntimeException $e) {
    if (str_contains($e->getMessage(), 'retrieving columns')) {
        $cols = DB::select('SELECT column_name, data_type FROM information_schema.columns WHERE table_name = ?', ['users']);
    } else {
        throw $e;
    }
}

Prevention

Bind a concrete grammar in every custom connection.
Implement compileColumns when authoring a new grammar - it underpins hasColumn, getColumnType, getColumnListing too.
Smoke-test migrations against the target engine in CI, not just SQLite.

When it happens

Trigger: Any column-introspection call (Schema::getColumns, hasColumn, getColumnType, getColumnListing) on a connection whose SchemaGrammar is the base Grammar. Typically a custom driver whose Connection::getDefaultSchemaGrammar() returns the base class.

Common situations: A community driver whose grammar was scaffolded but never implemented; a mocked test that injects the base Grammar; upgrading a driver package that temporarily removed overrides.

Related errors

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

Appendix: source

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

     * @throws \RuntimeException
     */
    public function compileTypes($schema)
    {
        throw new RuntimeException('This database driver does not support retrieving user-defined types.');
    }

    /**
     * Compile the query to determine the columns.
     *
     * @param  string|null  $schema
     * @param  string  $table
     * @return string
     *
     * @throws \RuntimeException
     */
    public function compileColumns($schema, $table)
    {
        throw new RuntimeException('This database driver does not support retrieving columns.');
    }

    /**
     * Compile the query to determine the indexes.
     *
     * @param  string|null  $schema
     * @param  string  $table
     * @return string
     *
     * @throws \RuntimeException
     */
    public function compileIndexes($schema, $table)
    {
        throw new RuntimeException('This database driver does not support retrieving indexes.');
    }

    /**
     * Compile a vector index key command.

View on GitHub (pinned to e0f6eb3518)