Laravel 11: Remove Doctrine DBAL

[hafezdivandari]

Description

Doctrine DBAL has been removed from Laravel 11.x:

• [11.x] Remove Doctrine DBAL laravel/framework#48864
• Laravel 11.x Upgrade Guide

This PR removes doctrine/dbal from filament and uses following Laravel's native schema methods, that are stable since Laravel 10.38, instead:

• Schema::getColumns($table)
• Schema::getColumnListing($table)
• Schema::getIndexes($table)

PS 1: It's my first time contributing to filament, please let me know if I've missed anything, and sorry about that!
PS 2: This PR targets laravel-11 branch (#10972), please let me know if you prefer anything else.
PS 3: I tried to keep the changes as minimum as possible, but this PR changes the methods' signatures on packages/support/src/Commands/Concerns/CanReadModelSchemas.php, IDK if you consider this as a breaking change or not.

Code style

• composer cs command has been run.

Testing

• Changes have been tested.

Documentation

• Documentation is up-to-date.

[hafezdivandari]

These column types are also possible, I put them here for you to do the mapping as you want. For example you may want to have a select input for enum column type.

[hafezdivandari]

Related to https://github.com/filamentphp/filament/pull/11429/files#r1491482327

You don't have any usage for these, but I put them here in case you wanted to add something in the future.

[danharrin]

Thank you

[sandersjj]

Hello, I am having an issue with this:

When I run this migration:

      Schema::table('products', function (Blueprint $table) {
            $table->integer('stock')->nullable()->change();
        });

I get the error that it needs Doctrine/DBAL

I am on Laravel 10.46

[danharrin]

You can install DBAL in your project as per the Laravel documentation, ideally you should not be relying on the fact that Filament had it installed by default since it is also in the Laravel instructions

[sandersjj]

I understand and I will install the package in my dev. But I find it weird. Shouldn't this PR break many more projects? Since this migration is quite up to date and is still be used in Laravel.

[danharrin]

If you want to submit a PR to add it back you can, but this does feel like mostly user error

[danharrin]

I'll just do it in the next release

[hafezdivandari]

@sandersjj on Laravel 10, you may call Schema::useNativeSchemaOperationsIfPossible() method within the boot method of your App\Providers\AppServiceProvider class. See laravel/framework#45487

[sandersjj]

@hafezdivandari thanks this works!