[FIX] Handle default table options in master slave connection. #453
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently the doctrine
AbstractSchemaManager::createSchemaConfig
is checking the top level of the settings array to see if thedefaultTableOptions
is set. When utilizing theMasterSlaveConnection
this setting is nested within themaster
andslave
arrays and is getting ignored.Changes proposed in this pull request:
MasterSlaveConnection::resolve()
function to check if this setting is set and add it to the top level of the returned array.MasterSlaveConnectionTest
to verify that thedefaultTableOptions
are being handle properly.