Asmir Mustafic

This issue is related to https://github.com/doctrine/migrations/pull/1071 Ideally https://github.com/doctrine/migrations/pull/1071 should not have been merged, but it causes issues with some database engines when exec is used (`addSql` uses `exec` or `prepare`...

TBH I do not know what is the expected behavior here... :(

> is considered new by the status calculator yes, exactly. since the migration has not been executed (skipped), when checking if there are new migrations, the command returns non-zero exit...

The issue is that we do not know if a migration is skipped or not until we do not run the `migrate` command. Skipped migrations are considered new migrations. `doctrine:migrations:up-to-date`...

https://github.com/doctrine/migrations/pull/1193 is the first step to fix this issue

This seems possible now thanks to https://github.com/doctrine/sql-formatter/pull/48

Hi, thanks for providing such detailed description of the issue. I wasn't aware of such subtle difference. So you are saying that it should be : ```xml ... ``` Right?...

I install the libraries using composer - - prefer-source, that will clone all the repos, then i create a new branch with phpstorm, that will create the same branche name...

Hi, the soap-server is not complete.... as you can see the last commit is more than a year ago. did not have to complete it. The other libs should work...

Hmm, I was hoping that someone would benefit from the existing code, and maybe help to make it working. IMO almost 70% of what is needed is already here..