Skip to content
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

Changes to allow doctrine/dbal 4 #41

Merged
merged 2 commits into from
Sep 7, 2024
Merged

Changes to allow doctrine/dbal 4 #41

merged 2 commits into from
Sep 7, 2024

Conversation

knallcharge
Copy link
Contributor

I have tried to make changes to allow the usage of doctrine/dbal 4.

getName() of Doctrine/Type was removed in dbal 4 (already deprecated in dbal 3), so I replaced it with TypeRegistry::lookup() which should do the job.
I don't know if running Type::getTypeRegistry for each column is a little too much overhead or if this should just be issued once and the object reused, but I didn't dive deep enough into the package to find out the necessary changes - you decide :)

Successfully tested this with one of my projects, please let me know what you think.

@jawira
Copy link
Owner

jawira commented Sep 5, 2024

Hi thank you for your pr, please give me some days to check this since I'm really busy right now.

@jawira jawira merged commit f324f12 into jawira:main Sep 7, 2024
0 of 4 checks passed
@jawira
Copy link
Owner

jawira commented Sep 7, 2024

Hello, thank you very much for this PR :)

@jawira
Copy link
Owner

jawira commented Sep 7, 2024

@knallcharge I just released v1.7.0 with DBAL 4 compatibility, thank you very much for reporting this and for the PR :)

@knallcharge
Copy link
Contributor Author

@jawira Thanks for the quick merge :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants