Skip to content

Conversation

@f1r3starter
Copy link

Update dependencies, fix deprecations notes, add migrations

@mbadolato
Copy link
Contributor

Just FYI, when running against postgres:

Screen Shot 2019-04-25 at 9 45 23 PM

@prolic
Copy link
Member

prolic commented Apr 26, 2019

Thanks for the hint @mbadolato. @f1r3starter can you update the PR?

@f1r3starter
Copy link
Author

@mbadolato Thanks for pointing out! Fixed
@prolic PR updated, also added commented postgresql block to docker-compose.yml and .env connection, just in case if someone would like to test it with postgres instead of mysql

@prolic
Copy link
Member

prolic commented Apr 30, 2019

@prooph/symfony-team please check

@mbadolato
Copy link
Contributor

Does a migration run when named something arbitrary? I always thought that Doctrine Migrations needed the naming scheme to match up what the latest is in the database and determine what is next and hasn't yet run.

@mbadolato
Copy link
Contributor

Hmm, yep as suspected. When I named the migration file the same as the last commit, the migration failed. Naming it back to the original and the migration ran.

Or is there a config setting that needs to be changed to allow?

Screen Shot 2019-05-01 at 9 27 34 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants