alwex/php-database-migration

Database Migration tool for PHP

php-database-migration's Issues

Environment variables in env files

Is it possible to use environment variables in env configurations? I populated database credentials into system env and would like to use it in migrations. Thanks!

The editor (vim) shouldn't be hardcoded, it should coming from the config.

php-database-migration/Migrate/Command/CreateCommand.php

Line 51 in 8f02441

system("vim $migrationFullPath > `tty`");

Status of project ?

Is this project anymore maintained ? I would like to with latest symfony but no luck due to old dependencies.

[Insight] Error silenced by the at sign (@) - in Migrate/Migration.php, line 180

in Migrate/Migration.php, line 180

Adding "@" before $content = file_get_contents($migrationDir . '/' . $this->getFile()) prevents warning and errors during this function execution from being displayed.
If you need to do that, you should probably implement a better way to qualify and recover from errors, using Exceptions.

        );
    }

    public function load($migrationDir)
    {
        @$content = file_get_contents($migrationDir . '/' . $this->getFile());
        if ($content && strpos($content, '@UNDO') > 0) {
            $sql = explode('-- @UNDO', $content);
            $this->setSqlUp($sql[0]);
            $this->setSqlDown($sql[1]);
        }

---

Posted from SensioLabsInsight

Update `symfony/console` to 4.x

symfony/console has been released, could you update it to 4.x or loosen dependency to 4.x?

Allow a custom changelog table

Allow a custom changelog table in the configuration file

Changelog

The tool should have a Changelog.md

Migrate Errors

Errors from failed SQL execution from migration files not displayed. The console shows 100% complete even when there was an error executing the SQL script at the database side. The changelog also changes regardless of problems in execution. This can lead to failed migrations seen as completed.

take account of .sql files only to avoid swap files

if someone push a bad file (wim sap for example) in the migrations path, it will be taken into account. The migrator may avoid the no .sql files