<!-- 
RSS generated by JIRA (5.2.7#850-sha1:b2af0c8dc8537b36121c6a579fabbdf79fc919e5) at Thu Jun 20 08:44:57 UTC 2013

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
For example:
http://www.doctrine-project.org/jira/si/jira.issueviews:issue-xml/DBAL-401/DBAL-401.xml?field=key&field=summary
-->
<rss version="0.92" >
<channel>
    <title>Doctrine Project</title>
    <link>http://www.doctrine-project.org/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>5.2.7</version>
        <build-number>850</build-number>
        <build-date>21-02-2013</build-date>
    </build-info>

<item>
            <title>[DBAL-401] Log connection info with SQL logger</title>
                <link>http://www.doctrine-project.org/jira/browse/DBAL-401</link>
                <project id="10040" key="DBAL">Doctrine DBAL</project>
                        <description>&lt;p&gt;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&lt;/p&gt;</description>
                <environment></environment>
            <key id="14334">DBAL-401</key>
            <summary>Log connection info with SQL logger</summary>
                <type id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="3" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/major.png">Major</priority>
                    <status id="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/resolved.png">Resolved</status>
                    <resolution id="2">Won&apos;t Fix</resolution>
                    <security id="10000">All</security>
                        <assignee username="beberlei">Benjamin Eberlei</assignee>
                                <reporter username="anandagra">Ananda Agrawal</reporter>
                        <labels>
                    </labels>
                <created>Fri, 28 Dec 2012 06:52:06 +0000</created>
                <updated>Fri, 28 Dec 2012 14:23:33 +0000</updated>
                    <resolved>Fri, 28 Dec 2012 08:50:02 +0000</resolved>
                                                                    <due></due>
                    <votes>0</votes>
                        <watches>2</watches>
                        <comments>
                    <comment id="19187" author="beberlei" created="Fri, 28 Dec 2012 08:50:02 +0000"  >&lt;p&gt;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&apos;t provide any useful loggers for production anyways this is up to your own logger.&lt;/p&gt;</comment>
                    <comment id="19191" author="anandagra" created="Fri, 28 Dec 2012 14:23:33 +0000"  >&lt;p&gt;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&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>
</channel>
</rss>