Skip to content


DBAL-519: MasterSlave connection does not keep Slave connections when there is a transaction #1724

doctrinebot opened this Issue · 3 comments

2 participants


Jira issue originally created by user anandagra:

while doing a transaction (as a result of ORM persist),
the connect function sets the forceMasterAsSlave which result on setting
slave to master,

on future selects, even if keepSlave is set to true
and connecting to 'slave' as ->connect('slave')
we will get master connections

I assume we need to check keepSlave when forcing slaves to master


Comment created by @deeky666:

Fixed in commit: 269d3e1


Issue was closed with resolution "Fixed"

@beberlei beberlei was assigned by doctrinebot
@doctrinebot doctrinebot added this to the 2.5 milestone
@doctrinebot doctrinebot closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.