<!--
RSS generated by JIRA (5.2.7#850-sha1:b2af0c8dc8537b36121c6a579fabbdf79fc919e5) at Fri May 24 21:19:02 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/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=fixVersion+%3D+%222.0.0-BETA4%22+AND+project+%3D+DBAL&tempMax=1000&field=key&field=summary
-->
<!-- If you wish to do custom client-side styling of RSS, uncomment this:
<?xml-stylesheet href="http://www.doctrine-project.org/jira/styles/jiraxml2html.xsl" type="text/xsl"?>
-->
<rss version="0.92">
    <channel>
        <title>Doctrine Project</title>
        <link>http://www.doctrine-project.org/jira/secure/IssueNavigator.jspa?reset=true&amp;jqlQuery=fixVersion+%3D+%222.0.0-BETA4%22+AND+project+%3D+DBAL</link>
        <description>An XML representation of a search request</description>
                <language>en-us</language>
                        <issue start="0" end="3" total="3"/>
                <build-info>
            <version>5.2.7</version>
            <build-number>850</build-number>
            <build-date>21-02-2013</build-date>
        </build-info>
<item>
            <title>[DBAL-39] SQL Logger should log the last failed query</title>
                <link>http://www.doctrine-project.org/jira/browse/DBAL-39</link>
                <project id="10040" key="DBAL">Doctrine DBAL</project>
                        <description>&lt;p&gt;The SQL Logger is only called after a query has been executed (this was changed to allow profiling of the queries).  This makes it difficult to determine which query has failed.&lt;/p&gt;

&lt;p&gt;The commit that changed the functionality is at: &lt;a href=&quot;http://github.com/doctrine/dbal/commit/fe0f0e4b8c6c5308cab3d683c552f61317de7067&quot; class=&quot;external-link&quot;&gt;http://github.com/doctrine/dbal/commit/fe0f0e4b8c6c5308cab3d683c552f61317de7067&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It seems that the logger interface needs to be changed to two functions, a pre-query function and a post-query function.  Profiling should be handled by the logger if it chooses and not by the connection class.&lt;/p&gt;</description>
                <environment></environment>
            <key id="11722">DBAL-39</key>
            <summary>SQL Logger should log the last failed query</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="1">Fixed</resolution>
                                <assignee username="beberlei">Benjamin Eberlei</assignee>
                                <reporter username="mridgway">Michael Ridgway</reporter>
                        <labels>
                    </labels>
                <created>Wed, 4 Aug 2010 14:24:09 +0000</created>
                <updated>Sun, 15 Aug 2010 14:57:22 +0000</updated>
                    <resolved>Sun, 15 Aug 2010 14:57:22 +0000</resolved>
                            <version>2.0.0-BETA3</version>
                                <fixVersion>2.0.0-BETA4</fixVersion>
                                        <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                        <comments>
                    <comment id="13958" author="beberlei" created="Sun, 15 Aug 2010 14:57:22 +0000"  >&lt;p&gt;After lots of thinking i changed the Logger again to have a startQuery() and a stopQuery() method now.&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[DBAL-38] Unused DBAL\Events (preExecute, postExecute)...</title>
                <link>http://www.doctrine-project.org/jira/browse/DBAL-38</link>
                <project id="10040" key="DBAL">Doctrine DBAL</project>
                        <description>&lt;p&gt;The ORM has a neat collection of Events, but the DBAL doesn&apos;t have any.&lt;br/&gt;
There is an DBAL/Events.php class which has defined constants for preExec, postExec, preExecute and postExecute (similar to ORM/Events.php), but these seem to be completely unused.&lt;br/&gt;
The only event/loging seems to be the -&amp;gt;logSql() event.&lt;/p&gt;


&lt;p&gt;A preExecute &amp;amp; postExecute events would be great for timing/profiling queries.&lt;/p&gt;</description>
                <environment>Linux</environment>
            <key id="10657">DBAL-38</key>
            <summary>Unused DBAL\Events (preExecute, postExecute)...</summary>
                <type id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/minor.png">Minor</priority>
                    <status id="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/resolved.png">Resolved</status>
                    <resolution id="1">Fixed</resolution>
                                <assignee username="beberlei">Benjamin Eberlei</assignee>
                                <reporter username="bjori">Hannes Magnusson</reporter>
                        <labels>
                    </labels>
                <created>Wed, 23 Dec 2009 13:00:15 +0000</created>
                <updated>Sun, 15 Aug 2010 14:59:41 +0000</updated>
                    <resolved>Sun, 15 Aug 2010 14:59:41 +0000</resolved>
                            <version>2.0.0-BETA3</version>
                                <fixVersion>2.0.0-BETA4</fixVersion>
                                        <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                        <comments>
                    <comment id="12378" author="jwage" created="Sat, 20 Mar 2010 01:48:15 +0000"  >&lt;p&gt;Roman, do we want to implement these? If so I can produce a patch.&lt;/p&gt;</comment>
                    <comment id="12407" author="romanb" created="Sat, 20 Mar 2010 15:19:54 +0000"  >&lt;p&gt;I&apos;m not sure of their usefulness. Hannes mentions timing queries but this is not really possible since many queries are &lt;b&gt;not&lt;/b&gt; executed through execute()/executeUpdate() but rather through prepare() and then execute() on the Statement.&lt;/p&gt;

&lt;p&gt;Are there any other good use-cases?&lt;/p&gt;</comment>
                    <comment id="12409" author="beberlei" created="Sat, 20 Mar 2010 16:28:57 +0000"  >&lt;p&gt;Hm timing and profiling could either be done with vendor-tools or we extend the SqlLogger interface a bit like i proposed in a previous issue. I dont see any other use-cases.&lt;/p&gt;</comment>
                    <comment id="12414" author="romanb" created="Sat, 20 Mar 2010 18:27:30 +0000"  >&lt;p&gt;Personally I find timing queries in php code not very useful since its very inaccurate and you dont get any further information.&lt;/p&gt;</comment>
                    <comment id="13040" author="shurakai" created="Fri, 21 May 2010 19:16:32 +0000"  >&lt;p&gt;If there are no other use cases, +1 for removal.&lt;/p&gt;</comment>
                    <comment id="13628" author="shurakai" created="Wed, 21 Jul 2010 05:38:05 +0000"  >&lt;p&gt;Has any decision been made on whether to remove or not?&lt;/p&gt;</comment>
                    <comment id="13727" author="romanb" created="Wed, 28 Jul 2010 17:32:29 +0000"  >&lt;p&gt;I think they can be removed as the DBAL SQLLogger now also records the execution time.&lt;/p&gt;</comment>
                    <comment id="13959" author="beberlei" created="Sun, 15 Aug 2010 14:59:41 +0000"  >&lt;p&gt;Removed!&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[DBAL-35] PDO_Sqlsrv bug in _constructPdoDsn()</title>
                <link>http://www.doctrine-project.org/jira/browse/DBAL-35</link>
                <project id="10040" key="DBAL">Doctrine DBAL</project>
                        <description>&lt;p&gt;When connection to mssql server with pdo_sqlsrv driver you get:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-none&quot;&gt; 
[PDOException]
SQLSTATE[IMSSP]: The DSN string ended unexpectedly.
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Sample $connectionOptions:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-none&quot;&gt;$connectionOptions = array(
    &apos;dbname&apos; =&amp;gt; &apos;AdventureWorks&apos;,
    &apos;user&apos; =&amp;gt; &apos;sa&apos;,
    &apos;password&apos; =&amp;gt; &apos;sa_password&apos;,
    &apos;host&apos; =&amp;gt; &apos;local&apos;,
    &apos;driver&apos; =&amp;gt; &apos;pdo_sqlsrv&apos;
);
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Error is in &lt;b&gt;Doctrine\DBAL\Driver\PDOSqlsrv\Driver&lt;/b&gt; in function &lt;b&gt;_constructPdoDsn(array $params)&lt;/b&gt;.&lt;br/&gt;
On &lt;b&gt;line 53&lt;/b&gt; dsn starts with &lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-none&quot;&gt;$dsn = &apos;sqlsrv:(&apos;;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;instead of &lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-none&quot;&gt;$dsn = &apos;sqlsrv:server=(&apos;;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;as written in offical Microsoft help which come with SQL Server Driver For PHP v2.&lt;/p&gt;</description>
                <environment>Windows 7, Zend Server CE, Sql Server driver for PHP v2</environment>
            <key id="11665">DBAL-35</key>
            <summary>PDO_Sqlsrv bug in _constructPdoDsn()</summary>
                <type id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/blocker.png">Blocker</priority>
                    <status id="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/resolved.png">Resolved</status>
                    <resolution id="1">Fixed</resolution>
                                <assignee username="beberlei">Benjamin Eberlei</assignee>
                                <reporter username="bostjan">Bostjan Oblak</reporter>
                        <labels>
                    </labels>
                <created>Wed, 21 Jul 2010 16:03:33 +0000</created>
                <updated>Tue, 31 Aug 2010 17:51:58 +0000</updated>
                    <resolved>Tue, 31 Aug 2010 17:51:58 +0000</resolved>
                            <version>2.0.0-BETA2</version>
                                <fixVersion>2.0.0-BETA4</fixVersion>
                                <component>Drivers</component>
                        <due></due>
                    <votes>1</votes>
                        <watches>1</watches>
                        <comments>
                    <comment id="13650" author="beberlei" created="Wed, 21 Jul 2010 17:19:41 +0000"  >&lt;p&gt;@Juozas can you evaluate this and possibly apply a fix?&lt;/p&gt;</comment>
                    <comment id="14203" author="beberlei" created="Tue, 31 Aug 2010 17:51:58 +0000"  >&lt;p&gt;Fixed&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>
</channel>
</rss>