[11.x] Added dropColumnsIfExists, dropColumnIfExists and dropForeignIfExists

[eusonlito]

This PR introduces the dropColumnsIfExists method in Builder and dropColumnIfExists / dropForeignIfExists in Blueprint.

These methods add a convenient way to safely drop columns from a table if they exist, preventing errors when the specified columns are absent.

While I am not entirely sure how to approach creating tests for this functionality, I have tested it extensively in my code with different migration scenarios. For example, I've tested it with columns that are present and others that are not, and in every case, no errors were thrown.

Here’s how the new methods can be used in migrations:

Schema::table('assignment', function (Blueprint $table) {
    $table->dropColumnIfExists('model');
    $table->dropColumnIfExists('text', 'remote_id');
});

Schema::table('bot', function (Blueprint $table) {
    $table->dropColumnIfExists('icebr');
    $table->dropColumnIfExists('text');
});

Schema::table('grade', function (Blueprint $table) {
    $table->dropColumnIfExists('submission');
    $table->dropForeignIfExists(['tutor_id']);
    $table->dropColumnIfExists('tutor_id');
    $table->dropColumnIfExists('response');
});

Our team uses a shared database across multiple applications, which requires us to frequently modify the database schema. The dropColumnIfExists functionality is essential for our workflow as it ensures that migrations run smoothly without being interrupted by missing columns. This enhancement could also be beneficial to others who work in environments where Laravel does not have complete control over the database schema, providing a more resilient and error-proof migration process.

Any feedback would be welcome.

Thanks!

[lk77]

This won't work on foreign keys, you will need to delete the constraint first

[eusonlito]

This won't work on foreign keys, you will need to delete the constraint first

Is the same behaviour as dropColumn.

[lk77]

yes, except that i can drop the foreign key before the column,
but i cannot drop a foreign key only when it exists, like i would need to, to be able to use your dropColumnIfExists.

[eusonlito]

yes, except that i can drop the foreign key before the column, but i cannot drop a foreign key only when it exists, like i would need to, to be able to use your dropColumnIfExists.

Done, also added dropForeignIfExists.

[MrPunyapal]

Awesome @eusonlito 👌

[eusonlito]

❤️

[hafezdivandari]

Seems I'm a bit late here! You can't call Schema facade directly on Blueprint, ignoring migration's connection and table's prefix. For example, Schema::connection('secondary')->dropColumnsIfExists('table', ['column']) checks if default.table.column exists and drops secondary.table.column.

Solution: use ifExists fluent attribute and move the logic to Schema\Grammar instead.

[eusonlito]

@hafezdivandari Thank you for your review. Could you open a PR here to fix this issue?

[hafezdivandari]

@eusonlito sure.

[hafezdivandari]

You may check #53337

Update: reverted on #53338