From b6c2489be8c4f935b1b498ef9fbefb0e8c64c18a Mon Sep 17 00:00:00 2001 From: Orkhan Ahmadov Date: Tue, 22 Sep 2020 13:59:02 +0200 Subject: [PATCH] Update README.md --- README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.md b/README.md index 794d56d..4c49ad1 100644 --- a/README.md +++ b/README.md @@ -23,6 +23,11 @@ But using Laravel's own migrations for this purpose have some drawback: * After some time it gets hard to manage and find content-based migrations among many migration files. * Recent introduction of "migration squashing" in Laravel 8 copies last state of database structure only. This means if you have content-based migrations you need to find a way to migrate them again if you have an empty database. +Laravel seeders are ideal for managing content in your database, but they also have their drawbacks: + +* They are not as automatic as migrations, you need to run and track each of them individually +* If you have an empty datatabase it becomes hard, almost impossible to know the order of seeders to run + This package aims to solve these problems by having dedicated content-based migrations separate from usual Laravel migrations. ## Requirements