TOPIC
Renaming a column, dropping one, and dropping a foreign key each have a specific gotcha — a dependency on doctrine/dbal for renames on older Laravel, and getting the foreign key's actual constraint name right for drops.
A seeder fills the database with rows — for lookup data every environment needs, or for realistic fake data during local development. Which one it is changes how you should write it.
Four common schema changes on an existing table — adding a column, giving it a default, indexing it, and adding an enum column — plus the one package they all quietly depend on for SQLite.
A migration is a version-controlled, reversible description of one schema change — the file, the up()/down() methods, and the commands that actually apply or undo it.
Changing a column type after it is already in production requires the doctrine/dbal package (or Laravel 11's native alternative) and a real rollback plan.
