-
-
Notifications
You must be signed in to change notification settings - Fork 223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fresh Neos installation with missing migrations #2475
Comments
Thanks for the issue. It's a known issue in a way. I saw this already, and figured we need to update things in our side. The reason for this might be many: subtle changes to Doctrine or DB defaults, forgotten migrations in the past development, … I'll check that carefully… |
One reason for differences detected in older setups (Neos 3.x): doctrine/orm#6565 - caused by a change in MariadDB 10.2 and fixed in DBAL 2.7. That causes changes that are no changes, like:
even though the table structure matches exactly. |
The
This can be properly done using annotations as of DBAL 2.9.0 (used in Neos 4.3 / Flow 5.3), see doctrine/dbal#2412 Even if doing that, generated migrations will pick up a DROP/CREATE cycle for that index. Doh. |
Some other changes are actually "forgotten" adjustments that we need to fix. |
Change index on "movedto" to unique (was forgotten) See neos#2475
As of Doctrine DBAL 2.9.2 this is actually possible, so we can finally do it right. See neos#2475
The name IDX_35DC14F03332102A is different from what Doctrine does auto-generate, but needs to be used due to BC reasons with existing migrations. See neos/neos-development-collection#2475
Change index on "movedto" to unique (was forgotten) See neos#2475
Still open:
as these are not part of the development distribution… |
Note there will still be some differences to be detected, due to mismatches between what the DB reports and what Doctrine thinks it should report. That is true for MySQL/MariaDB as well as PostgreSQL. |
The |
The |
The name IDX_35DC14F03332102A is different from what Doctrine does auto-generate, but needs to be used due to BC reasons with existing migrations. See neos/neos-development-collection#2475
Description
A fresh Neos installation has missing migrations. But when you run them they result in a SQL error.
Steps to Reproduce
./flow doctrine:migrationgenerate
Expected behavior
There shouldn't be any migrations classes to be generated.
Actual behavior
There is a migrations class created with the following content:
When you run
./flow doctrine:migrate
after the creation the following error occurs:Affected Versions
Neos: 4.3.0
Flow: 5.3.0
PHP: 7.3.4
MariDB: 10.3.14
The text was updated successfully, but these errors were encountered: