Populating a database in a Laravel migration file

Question

I m just learning Laravel  and have a working migration file creating a users table  I am trying to populate a user record as part of the migration   public function up         Schema  create  users   function  table             table- gt increments  id             table- gt string  email   255            table- gt string  password   64            table- gt boolean  verified             table- gt string  token   255            table- gt timestamps             DB  table  users  - gt insert              array                   email    gt   name domain com                    verified    gt  true                                       But I m getting the following error when running php artisan migrate   SQLSTATE 42S02   Base table or view not found  1146 Table  vantage users  doesn t exist   This is obviously because Artisan hasn t yet created the table  but all the documentation seems to say that there is a way of using Fluent Query to populate data as part of a migration   Anyone know how  Thanks

User · Answer

I tried this DB insert method  but as it does not use the model  it ignored a sluggable trait I had on the model  So  given the Model for this table exists  as soon as its migrated  I figured the model would be available to use to insert data  And I came up with this   public function up             Schema  create  parent categories   function  Blueprint  table                 table- gt bigIncrements  id                 table- gt string  name                 table- gt string  slug                 table- gt timestamps                        ParentCategory  create                                 id    gt  1                   name    gt   Occasions                                     This worked correctly  and also took into account the sluggable trait on my Model to automatically generate a slug for this entry  and uses the timestamps too  NB  Adding the ID was no neccesary  however  I wanted specific IDs for my categories in this example  Tested working on Laravel 5 8

User · Answer

Don t put the DB  insert   inside of the Schema  create    because the create method has to finish making the table before you can insert stuff  Try this instead   public function up            Create the table     Schema  create  users   function  table            table- gt increments  id             table- gt string  email   255            table- gt string  password   64            table- gt boolean  verified             table- gt string  token   255            table- gt timestamps                    Insert some stuff     DB  table  users  - gt insert          array               email    gt   name domain com                verified    gt  true

User · Answer

Here is a very good explanation of why using Laravel s Database Seeder is preferable to using Migrations  https   web archive org web 20171018135835 http   laravelbook com laravel-database-seeding  Although  following the instructions on the official documentation is a much better idea because the implementation described at the above link doesn t seem to work and is incomplete   http   laravel com docs migrations database-seeding

User · Answer

This should do what you want   public function up         DB  table  user  - gt insert array  username   gt  dude    password   gt  z19pers

User · Answer

I know this is an old post but since it comes up in a google search I thought I d share some knowledge here   erin-geyer pointed out that mixing migrations and seeders can create headaches and  justamartin countered that sometimes you want need data to be populated as part of your deployment   I d go one step further and say that sometimes it is desirable to be able to roll out data changes consistently so that you can for example deploy to staging  see that all is well  and then deploy to production with confidence of the same results  and not have to remember to run some manual step    However  there is still value in separating out the seed and the migration as those are two related but distinct concerns  Our team has compromised by creating migrations which call seeders  This looks like   public function up         Artisan  call   db seed              --class    gt   SomeSeeder            --force    gt  true              This allows you to execute a seed one time just like a migration  You can also implement logic that prevents or augments behavior  For example   public function up         if   SomeModel  count    lt  10                 Artisan  call   db seed                  --class    gt   SomeSeeder                --force    gt  true                        This would obviously conditionally execute your seeder if there are less than 10 SomeModels  This is useful if you want to include the seeder as a standard seeder that executed when you call artisan db seed as well as when you migrate so that you don t  double up   You may also create a reverse seeder so that rollbacks works as expected  e g   public function down         Artisan  call   db seed              --class    gt   ReverseSomeSeeder            --force    gt  true              The second parameter --force is required to enable to seeder to run in a production environment

User · Answer

Another clean way to do it is to define a private method which create instance et persist concerned Model   public function up         Schema  create  roles   function  Blueprint  table             table- gt increments  id             table- gt string  label   256            table- gt timestamps             table- gt softDeletes                  this- gt postCreate  admin    user       private function postCreate string     roles         foreach   roles as  role             model   new Role             model- gt setAttribute  label    role            model- gt save              With this solution  timestamps fields will be generated by Eloquent   EDIT  it s better to use seeder system to disctinct database structure generation and database population

User · Answer

If you already have filled columns and have added new one or you want to fill out old column with new mock values   do this   public function up         DB  table  foydabars  - gt update          array               status    gt   0

[php] Populating a database in a Laravel migration file

Examples related to php

Examples related to laravel

Examples related to migration

Examples related to mysql-error-1146