-
-
Notifications
You must be signed in to change notification settings - Fork 385
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
Error The metadata storage is not up to date
since 3.5.3
#1302
Comments
Here the same. php 7.4 symfony 5.4 |
My solution was to downgrade to 5.3.2
|
This is the table diff that is reported here:
|
Our Symfony 5.4 projects are also impacted by this issue, running MariaDB 10.6.9. Downgrading doctrine/migrations to 3.5.2 fixed the issue. |
Same happened over here. I'm using the library natively with MariaDB and changing Downgrading to 3.5.2 fixed it. |
Same issue here. |
The difference is on the "_platformOptions" for me.
On $toTable:
I would say introduced in this commit 1f58518 Reverting method needsUpdate() from TableMetadataStorage fix the problem on my side
|
Same here, not getting the charset en collation. so its see a diff every time |
@axi (or anybody) there are 3 changes in that method, it might be interesting to revert only one of them. |
Also @axi, On which column(s) do you observe the diff? |
I think something must be calling migrations/lib/Doctrine/Migrations/Metadata/Storage/TableMetadataStorage.php Lines 241 to 256 in 01f89a1
Can one of you determine if that's the case? I'm suspecting https://github.com/doctrine/dbal/blob/3.5.x/src/Platforms/MySQL/Comparator.php#L62 What's very interesting is the comment on that class: https://github.com/doctrine/dbal/blob/e106ee7a3869a2ca82b0993914ea55061be02554/src/Platforms/MySQL/Comparator.php#L15-L17
If I understand correctly, the diff should be empty if |
nice catch @greg0ire . As discussed on Slack the issue was the missing normalization of columns: doctrine/dbal#5861 |
Same here. Symfony 6.2, PHP 8.1, Mariadb 10.5.15 |
Please stop with the spam. |
Fixed by https://github.com/doctrine/dbal/releases/tag/3.5.3 (don't get confused, it's another package, it just happens to have the same version number) |
@greg0ire I've tried updating again with composer update but the error persist. Forcing a downgrade to 3.5.2 and then reupgrading do 3.5.3 didn't work. removing the package and readding also did not fix. Here is a
and here is my composer.json
|
Ok, removing from require-dev the |
Lol what |
@samuel-sol reading your first message, it sounds like you downgraded doctrine/migrations to 2.5.2, then upgraded again to 2.5.3, expecting the bug to be somehow fixed… if that's the case, I suggest you read #1302 (comment) again, but slowly. |
Same problem here with MySQL
|
If you are using getsentry/sentry-symfony this could be related |
Same problem for me .... I'm on doctrine/migrations 3.6.0 |
EDIT: I realize that this is an old issue, but this just came up on my project and I cannot see in the comments above, a clear indication of what is causing this or how to go about finding the correct solution.
@greg0ire This does not seem to solve the problem in all cases. Here's a dump of the
|
Since OP seems to be satisfied with this, it means this is a different issue with the same symptoms. You should open another issue if there isn't one already about this |
@greg0ire I might. I have a feeling this is some incompatibility between some doctrine component and the mariadb version we're running. I've seen more instances of quoted NULL strings in the migration I was able to create by temporarily deactivating the |
OK. In the meantime, I'll lock this, as the error message can be caused by many different reasons. |
Bug Report
Summary
I just upgraded to 3.5.3 and I have an error when running
app/console doctrine:migrations:up-to-date
:Unfortunately running
doctrine:migrations:sync-metadata-storage
does not help. It says[OK] Metadata storage synchronized
but I get the same error when runningup-to-date
again.How to reproduce
This is my metadata table dump
Expected behavior
It should not report an issue with out-of-sync storage
The text was updated successfully, but these errors were encountered: