Which option do you like best for migration and seed?
<ol>
<li>Option A</li>
<li>Option B</li>
</ol>
#php #Laravel

Welcome to PHP Dev, a dedicated space for sharing knowledge about PHP and its ecosystem (only PHP directly related).
Help us find good articles and blogposts and provide links. Upvote or downvote, after reading, it's essential

PHP Dev

The post discusses two options for performing migration and seeding tasks in Laravel, inviting readers to share their preferences between Option A and Option B.

Laravel Tip

actualy setup short hand for php artisan to pa and if i have to use migration pam and with seeding i would set it to pams. would save you finger from typing them again and again a lot.

Option B is a definitely way to go.

just an example:
lets say that we want a seeder a new table eg. a notes table
and we need to initialize it with some notes.
PHP artisan make:seeder NotesSeeder
we are getting some notes. for example by parsing our excel file and we are writing code to that inserting the rows from our excel file or we are creating a pipelinefrom an old database to out current database though eloquent or through query builder (doesn’t matter).
now we need to seed these notes.
PHP artisan db:seed --class=NotesSeeder
and that’s it. I forgot that we ve migrated the dibi first with PHP artisan migrate.
when you are giving tips and tricks you have to take care about real world. in real world the applications scale. their db too. the 2nd command is useful only for the first installation of the application. it doesn’t work when your application scale. the second option can work every time.