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

Make master connections respect driverOptions #1253

Merged

Conversation

petewalker
Copy link
Contributor

Reverts the changes made in #1240, and applies the passing down of driverOptions manually in CreateDatabaseDoctrineCommand and DropDatabaseDoctrineCommand

Resolves #1252

I haven't written any tests for this - it seems that these commands aren't particularly testable due to the static call to DriverManager::getConnection. It's not straightforward to verify the params that are passed to it. I considered refactoring the seemingly common code in both commands into a single parent methods, but there's slight differences between them that makes me wary of breaking something.

…verOptions

Reverts the changes made in doctrine#1240, and applies the passing down of `driverOptions` manually in `CreateDatabaseDoctrineCommand` and `DropDatabaseDoctrineCommand`

Resolves doctrine#1252
@ostrolucky ostrolucky added this to the 2.2.1 milestone Nov 10, 2020
@ostrolucky ostrolucky changed the title fix: Revert #1240 and allow master connections to respect driverOptions Make master connections respect driverOptions Nov 10, 2020
@ostrolucky ostrolucky merged commit 5a94ec5 into doctrine:1.12.x Nov 10, 2020
@ostrolucky ostrolucky modified the milestones: 2.2.1, 1.12.13 Nov 10, 2020
simPod added a commit to simPod/DoctrineBundle that referenced this pull request Apr 11, 2022
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.

MasterSlaveConnection with driverOptions now broken outside of create/drop commands
2 participants