namespace IlluminateDatabaseConsoleMigrations;
use IlluminateConsole/confirm/iableTrait;
use IlluminateDatabaseMigrationsMigrator;
use SymfonyComponentConsoleInputInputOption;
class MigrateCommand extends baseCommand
{// Migrate Command extends base Command
use /confirm/iableTrait;
protected $name = 'migrate';//The console command name.
protected $description = 'Run the database migrations';// description
protected $migrator;// instance of this class of migrator
public function __construct(Migrator $migrator)
{
parent::__construct();
$this->migrator = $migrator;
}// Create a new migration command instance.
public function fire()
{
if (! $this->confirmToProceed()) {
return;
}//fire that just execute the console command
$this->prepareDatabase();// prepareDatabase just like general
// The pretend option can be used for "simulating" the migration and grabbing
// the SQL queries that would fire if the migration were to be run against
// a database for real, which is helpful for double checking migrations.
$pretend = $this->input->getOption('pretend');
// simulating: to make a thing like you want
// grabbing: catch or get
// this is pretend to double checking migration
// Next, we will check to see if a path option has been defined. If it has
// we will use the path relative to the root of this installation folder
// so that migrations may be run for any path within the applications.
if (! is_null($path = $this->input->getOption('path'))) {
$path = $this->laravel->basePath().'/'.$path;
} else {
$path = $this->getMigrationPath();
}// if does not has the path option,we will set a default place.other maybe in anywhere.
$this->migrator->run($path, [
'pretend' => $pretend,
'step' => $this->input->getOption('step'),
]);// set fire or execute with path and pretend even this step
// once the migrator has run we will grab the note output and send it out to
// the console screen, since the migrator itself functions without having
// any instances of the OutputInterface contract passed into the class.
foreach ($this->migrator->getNotes() as $note) {
$this->output->writeln($note);
}// write the notes in log or in output
// just a mind ,it too great!
// Finally, if the "seed" option has been given, we will re-run the database
// seed task to re-populate the database, which is convenient when adding
// a migration and a seed at the same time, as it is only this command.
if ($this->input->getOption('seed')) {
$this->call('db:seed', ['--force' => true]);
}// if has this "seed" order, then we must run it.
}
protected function prepareDatabase()
{//prepare Database
$this->migrator->setConnection($this->input->getOption('database'));
// connection
if (! $this->migrator->repositoryExists()) {
$options = ['--database' => $this->input->getOption('database')];
$this->call('migrate:install', $options);
}
}// call the migrate install is very good type.
protected function getOptions()
{// Get the console command options.
return [
['database', null, InputOption::VALUE_OPTIONAL, 'The database connection to use.'],
['force', null, InputOption::VALUE_NONE, 'Force the operation to run when in production.'],
['path', null, InputOption::VALUE_OPTIONAL, 'The path of migrations files to be executed.'],
['pretend', null, InputOption::VALUE_NONE, 'Dump the SQL queries that would be run.'],
['seed', null, InputOption::VALUE_NONE, 'Indicates if the seed task should be re-run.'],
['step', null, InputOption::VALUE_NONE, 'Force the migrations to be run so they can be rolled back individually.'],
];
}// Get the console command options.
}
