doctrine / migrations

 */

class ExecuteCommand extends AbstractCommand

{

    protected function configure()

    {

        $this

            ->setName('migrations:execute')

            ->setDescription('Execute a single migration version up or down manually.')

            ->addArgument('version', InputArgument::REQUIRED, 'The version to execute.', null)

            ->addOption('write-sql', null, InputOption::VALUE_NONE, 'The path to output the migration SQL file instead of executing it.')

            ->addOption('dry-run', null, InputOption::VALUE_NONE, 'Execute the migration as a dry run.')

            ->addOption('up', null, InputOption::VALUE_NONE, 'Execute the migration up.')

            ->addOption('down', null, InputOption::VALUE_NONE, 'Execute the migration down.')

            ->addOption('query-time', null, InputOption::VALUE_NONE, 'Time all the queries individually.')

            ->setHelp(<<<EOT

The <info>%command.name%</info> command executes a single migration version up or down manually:

    <info>%command.full_name% YYYYMMDDHHMMSS</info>

If no <comment>--up</comment> or <comment>--down</comment> option is specified it defaults to up:

    <info>%command.full_name% YYYYMMDDHHMMSS --down</info>

You can also execute the migration as a <comment>--dry-run</comment>:

    <info>%command.full_name% YYYYMMDDHHMMSS --dry-run</info>

You can output the would be executed SQL statements to a file with <comment>--write-sql</comment>:

    <info>%command.full_name% YYYYMMDDHHMMSS --write-sql</info>

Or you can also execute the migration without a warning message which you need to interact with:

    <info>%command.full_name% YYYYMMDDHHMMSS --no-interaction</info>

EOT

        );

        parent::configure();

    }

    public function execute(InputInterface $input, OutputInterface $output)

    {

     */

    private $markMigrated;

    protected function configure()

    {

        $this

            ->setName('migrations:version')

            ->setDescription('Manually add and delete migration versions from the version table.')

            ->addArgument('version', InputArgument::OPTIONAL, 'The version to add or delete.', null)

            ->addOption('add', null, InputOption::VALUE_NONE, 'Add the specified version.')

            ->addOption('delete', null, InputOption::VALUE_NONE, 'Delete the specified version.')

            ->addOption('all', null, InputOption::VALUE_NONE, 'Apply to all the versions.')

            ->addOption('range-from', null, InputOption::VALUE_OPTIONAL, 'Apply from specified version.')

            ->addOption('range-to', null, InputOption::VALUE_OPTIONAL, 'Apply to specified version.')

            ->setHelp(<<<EOT

The <info>%command.name%</info> command allows you to manually add, delete or synchronize migration versions from the version table:

    <info>%command.full_name% YYYYMMDDHHMMSS --add</info>

If you want to delete a version you can use the <comment>--delete</comment> option:

    <info>%command.full_name% YYYYMMDDHHMMSS --delete</info>

If you want to synchronize by adding or deleting all migration versions available in the version table you can use the <comment>--all</comment> option:

    <info>%command.full_name% --add --all</info>

    <info>%command.full_name% --delete --all</info>

If you want to synchronize by adding or deleting some range of migration versions available in the version table you can use the <comment>--range-from/--range-to</comment> option:

    <info>%command.full_name% --add --range-from=YYYYMMDDHHMMSS --range-to=YYYYMMDDHHMMSS</info>

    <info>%command.full_name% --delete --range-from=YYYYMMDDHHMMSS --range-to=YYYYMMDDHHMMSS</info>

You can also execute this command without a warning message which you need to interact with:

    <info>%command.full_name% --no-interaction</info>

EOT

            );

        parent::configure();

    }

    public function execute(InputInterface $input, OutputInterface $output)

    {