http://www.doctrine-project.org/jira This file is an XML representation of an issue en-us 5.2.7 850 21-02-2013 http://www.doctrine-project.org/jira/browse/DBAL-436 Doctrine DBAL <p>Suppose there is a master connection with four slaves specified. Connections are being handled by the Doctrine\DBAL\Connections\MasterSlaveConnection class. Under the current implementation, all queries are logged under the "master" connection, even queries that are routed to the slaves by the Doctrine\DBAL\Connections\MasterSlaveConnection class.</p> <p>Since slave connections are separate, distinct connections, queries should be logged appropriately under their respective connections.</p> DBAL-436

Logger should specify connection used in a master/slave situation

Bug Major Resolved Invalid All Benjamin Eberlei Jarrod Nettles Thu, 31 Jan 2013 22:47:28 +0000 Mon, 1 Apr 2013 16:34:12 +0000 Mon, 1 Apr 2013 16:34:12 +0000 2.3.2 2.3.3 0 2 <p>Two reasons why this is not feasible:</p> <p>1. We actually don't ship loggers on our own, so if you want you can implement this yourself. We wouldn't have a way to "add" this, we only provide the interface.</p> <p>2. However the logger does not have access to the connection to find out which slave or master its currently using, you can create a logger that has a "setConnection($conn)" method and call this during bootstrapping the logger+connection.</p>