Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[Messenger] Make Doctrine connection ignore unrelated tables on setup#54392
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
GromNaN left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
LGTM. Thanks for the test.
fabpot commentedApr 8, 2024
Thank you@MatTheCat. |
chriskapp commentedMay 4, 2024
In our case this PR breaks on postgres if a newer version of doctrine dbal is used since the filter receives also This issue is also already fixed by@xabbuh s. So for others searching this issue, we only need to wait for the next v6.4.8 release. |
thePanz commentedMay 8, 2024
For reference:#54775 |

Introspecting the whole database can cause issues like Doctrine crashing on unknown column types. This PR updates the schema assets filter (added by#31625) to only consider the messages table, as it is the only one a connection setup needs to care about.