Closed aprokopenko closed 2 months ago
Report this to Laravel, please.
But TimestampType in your code really doesn't have case for new platform added and it generate a fatal error in case you try to use it.
Is TimestampType
really in our code? Please provide a Github link to TimestampType
. In general, please provide links to things you refer to.
Sorry, maybe was a hard week, re-checked and this is really Laravel class.
No worries, have a nice end of week :)
That match statement you quoted is brittle and will continue to break with new DBAL releases or if you dare to override the platform. But it's not our code, so we can't do much about it.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Bug Report
Summary
After upgrade to 3.9.0 my migrations stop working (I'm using Laravel, which under the hood use your package). Create tables works fine, but all alters fail.
Current behaviour
After upgrade I have such error:
Returning back to 3.8.7 works totally fine. I have PostgreSQL 16.1. The platform is detected now as PostgreSQL120Platform, but it doesn't added everywhere inside the code, for example in TimestampType, the swtch looks like this and miss this class to identify sql declaration syntax:
How to reproduce
Didn't created test project with clean Doctrine, but for me my migrations for create table works find and alter queries (for change default value for example of the column - fails)
Expected behaviour
No fatal errors in new releases :)