GitLab

Add regex schema_filter behaviour into createFromSchema as createToSchema do to help fix/workaround remaining CREATE TABLEs in down migration.

Check for all-or-nothing conflict in migrations

Fixes https://github.com/doctrine/migrations/issues/1166

Bugfix: all-or-nothing from configuration must not be ignored

Box is not compatible with it yet.

The default value for all-or-nothing makes the command line option
always exist and the configuration option always ignored.

cache some metadata state to avoid querying all the time the database…

Update the default migration template to adhere to PSR 12 formatting

Fix phpstan workflow

It allows to simplify code in a test, and since compatibility with old
versions of PHP has been restored in 2.13.0, that should be ok.

Merge 2.3.x up into 3.1.x

Rollback if and only if inside a transaction

You cannot get an integer from the CLI, so it makes no sense to use an
integer as the default option.

Similarly to what happens when attempting to commit an already closed
connection when combining PHP 8 and pdo_mysql, an error is thrown when
attempting to rollback. We use the same solution as for commit(), that
is we check that we actually are inside a transaction when possible to do so.

Fixes #1139

[Doc] Fixed Syntax error in JSON Configuration File

There were syntax errors in the sample JSON configuration file:
1. a comma was missing
2. backslashes were not escaped

Maintenance work

# Conflicts:
#	lib/Doctrine/Migrations/Migrator.php
#	lib/Doctrine/Migrations/Tracking/TableUpdater.php
#	lib/Doctrine/Migrations/Version/Executor.php
#	lib/Doctrine/Migrations/Version/Factory.php

MySQL commits implicitly after every DDL query, but since PHP 8, mysql_pdo started to throw exception when attempting to explicitly commit after it implicitly committed. This causes to interrupt the migration process even though all queries completed successfully.

Alternative would be to disable transaction for PHP8+pdo_mysql, but that would affect all queries, not only DDL ones like intended, hence going with guard check before each explicit commit.

Hopefully this will be fixed directly in DBAL in future, but so far this doesn't look very likely...