DBAL-401: Log connection info with SQL logger #1594

Closed
doctrinebot opened this Issue Dec 28, 2012 · 3 comments

2 participants

@doctrinebot

Jira issue originally created by user anandagra:

while using MasterSlave connection, it would be nice to see the connection being used ( master or which slave), this will help debug the app, if lots read queries are going to Master

@doctrinebot

Comment created by @beberlei:

It is possible already, when you have a logger that has access to the connection again. MasterSlaveConnection#isConnectedToMaster() can be used to check. Since we don't provide any useful loggers for production anyways this is up to your own logger.

@doctrinebot

Issue was closed with resolution "Won't Fix"

@doctrinebot

Comment created by anandagra:

thanks Eberlei, when using SQLLogger I donot get much information other than the query and params etc, I am using DebugStack or willing to extend it but Connection objects looks like they donot send much info, is there a way this could be achieved

@beberlei beberlei was assigned by doctrinebot Dec 6, 2015
@doctrinebot doctrinebot closed this Dec 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment