Laravel 11: Be Careful with Changing Columns in Migrations

preview_player
Показать описание
A new Laravel 11 behavior that is the opposite of previous versions.

- - - - -
Support the channel by checking out my products:

- - - - -
Other places to follow:
  1. Laravel Daily
Рекомендации по теме
Laravel 11: Be 0:01:00

Laravel 11: Be Careful with Changing Columns in Migrations

Laravel DB Transactions 0:03:03

Laravel DB Transactions and Observers: Be Careful

Laravel Eloquent: Be 0:02:53

Laravel Eloquent: Be Careful with Select and withCount ORDER

Laravel: Be Careful 0:03:56

Laravel: Be Careful with whereHas Performance in Eloquent

Laravel 11 — 0:13:57

Laravel 11 — основные изменения и мое мнение

Laravel 11: Middleware 0:05:05

Laravel 11: Middleware and Exceptions in boostrap/app.php

Laravel 11 Tutorial 1:22:20

Laravel 11 Tutorial for Beginners - Laravel Crash Course (2024)

Easily upgrade to 0:05:14

Easily upgrade to Laravel 11 with Laravel Shift

Laravel 11: Image 0:56:08

Laravel 11: Image Upload & CRUD Made Easy!

Laravel Code Review: 0:09:33

Laravel Code Review: Optimize Queries and Other Performance

Laravel 11 API 0:18:42

Laravel 11 API CRUD app with Authentication using Laravel Sanctum course 2024 | Part 1/2

Laravel and Redis: 0:09:59

Laravel and Redis: The Absolute Basics

30 Days to 0:08:40

30 Days to Learn Laravel, Ep 01 - Hello, Laravel

LARAVEL 11 Crash 0:05:21

LARAVEL 11 Crash Course for Beginners 2024 | #5 Database Migrations (Web Developer Path)

Session Management in 0:11:30

Session Management in Laravel — Beyond the Basics

Laravel 11 + 5:44:19

Laravel 11 + React Full Stack App with Inertia - Project Management App

30 Days to 8:29:59

30 Days to Learn Laravel - Complete 8 Hour Course

Laravel 11 Upgrade 0:08:34

Laravel 11 Upgrade in Practice: Shift Example

LARACON EU 2024 1:10:48

LARACON EU 2024 // TAYLOR OTWELL :: LARAVEL UPDATE

Laravel Translations: Store 0:07:34

Laravel Translations: Store in PHP or JSON Files?

Laravel Eloquent | 0:04:01

Laravel Eloquent | take care before using upsert method

12 Laravel/PHP Tips 0:08:36

12 Laravel/PHP Tips in 8 Minutes: August 2024

How to Upgrade 0:01:59

How to Upgrade or Downgrade Laravel Version Safely

Learnings from our 0:09:58

Learnings from our multi-tenant Laravel application

Комментарии
Автор

The reason for this change is because laravel 11 rewrites the migration process to remove doctrine/dbal as dependency.

This dependency is there solely for changing table columns in sqlite, but it was used for any RDBMS you used. The worst part is that, doctrine/dbal has been used as custom type mappings for your specific RDBMS, but never fully utilized in laravel even though it was supported.

As such, now you must redeclare all attributes for changing your column. I see this change as a small compromise over having doctrine/dbal for just changing columns.

The benefit is that, now the column change migration is self-documented, and actually much clearer of what the expected result should be.

gtdmg
Автор

OMG imp info.. i frequently change columns

shubhamsahuSD
Автор

Column definitions are stored in MySQL, so the migration can read it and only change what the dev asked to change. Something like $column->nullable(false) could do? I love and recommend Laravel, please have a proper fix for this, this new behavior feels like a downgrade : not intuitive and breaks backward compatibility.

pominglam
Автор

this only when you want to change right?

ArshAudioBooks
Автор

A change that breaks backwards compatibility that I don't understand... for the MySQL driver it wasn't necessary... as for any relational DSBMS... I can always modify only the "nullable" attribute of a column...
Changing the default in this way forces those who have not yet done squash to revise the migrations backwards!!!!

MarcoAcorte
Автор

It's a nonsense breaking change 😮

MarcoAcorte