Differences

This shows you the differences between two versions of the page.

--- seeder [2020/12/23 19:08] – chifek
+++ seeder [2023/09/14 06:06] (current) – external edit 127.0.0.1
@@ Line 76: / Line 76: @@
 Within the `DatabaseSeeder` class, you may use the `call` method to execute additional seed classes. Using the call method allows you to break up your database seeding into multiple files so that no single seeder class becomes too large. The `call` method accepts an array of seeder classes that should be executed:
+<code>
+/**
+ * Run the database seeders.
+ *
+ * @return void
+ */
+public function run()
+{
+    $this->call([
+        UserSeeder::class,
+        PostSeeder::class,
+        CommentSeeder::class,
+    ]);
+}
+</code>
+**Running Seeders**
+You may execute the `db:seed` Artisan command to seed your database. By default, the `db:seed` command runs the `Database\Seeders\DatabaseSeeder` class, which may in turn invoke other seed classes. However, you may use the --class option to specify a specific seeder class to run individually:
+<code>
+php artisan db:seed
+php artisan db:seed --class=UserSeeder
+</code>
+You may also seed your database using the `migrate:fresh` command in combination with the `--seed` option, which will drop all tables and re-run all of your migrations. This command is useful for completely re-building your database:
+<code>
+php artisan migrate:fresh --seed
+</code>
+**Forcing Seeders To Run In Production**
+Some seeding operations may cause you to alter or lose data. In order to protect you from running seeding commands against your production database, you will be prompted for confirmation before the seeders are executed in the `production` environment. To force the seeders to run without a prompt, use the `--force` flag:
+<code>php artisan db:seed --force</code>