-
-
Notifications
You must be signed in to change notification settings - Fork 224
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
TASK: Fix MySQL migration differences on fresh setup #4236
Conversation
Hu i must have lost track of this :D Should we still target 7.3 (last bugfix) or rather 8.3 to be safe? |
I changed the base branch once, but could you please rebase on 8.3 and check if the pr is still correct ^^ |
Will check… |
9edfda4
to
674d0e2
Compare
With 8.3 this now gives me:
|
Thx, did you check if Postgres is also affected? |
If only I could remember. Maybe? It probably needs to be updated yet again, anyway… |
Current output with new Neos 8.3 is:
And after appling this PR:
|
@Sebobo Can we merge this anyways? If there are postgress issues we can handle that also in a dedicated PR. This is open for almost two years now and I'd like to merge it to improve the mysql usage experience. |
Yes sure, I mean the title also says mysql |
the package Neos.ContentRepository does not exist in Neos 9 In neos#4240 we removed all ContentRepository migrations so this is to be removed as well.
…rged-migration TASK: Followup #4236 remove legacy core migration
This eliminates some differences in the actual vs the expected DB setup in a fresh
Neos 8.3 installation.
Fixes #3118 (at least partly.)
Review instructions
doctrine:migrationgenerate
should just sayNo changes detected
after Neos has been set up.Checklist
Tests have been created, run and adjusted as neededFEATURE|TASK|BUGFIX
!!!
and have upgrade-instructions