<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Thu May 23 11:33:17 CDT 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.couchbase.com/issues/si/jira.issueviews:issue-xml/PCBC-134/PCBC-134.xml?field=key&field=summary
-->
<rss version="0.92" >
<channel>
    <title>Couchbase</title>
    <link>http://www.couchbase.com/issues</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>5.2.4</version>
        <build-number>845</build-number>
        <build-date>26-12-2012</build-date>
    </build-info>

<item>
            <title>[PCBC-134] Provide more information on connection failure</title>
                <link>http://www.couchbase.com/issues/browse/PCBC-134</link>
                <project id="10049" key="PCBC">Couchbase PHP client library</project>
                        <description>When you connect via the new Couchbase(...) is not a direct way to check for whether the connection failed. &lt;br/&gt;
&lt;br/&gt;
It is not possible to check getResultCode()/getResultMessage() since this provides a unintilized couchbase</description>
                <environment></environment>
            <key id="20130">PCBC-134</key>
            <summary>Provide more information on connection failure</summary>
                <type id="1" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="3" iconUrl="http://www.couchbase.com/issues/images/icons/priorities/major.png">Major</priority>
                    <status id="5" iconUrl="http://www.couchbase.com/issues/images/icons/statuses/resolved.png">Resolved</status>
                    <resolution id="1">Fixed</resolution>
                    <security id="10011">Public</security>
                        <assignee username="mjackson">Michael Jackson</assignee>
                                <reporter username="akadna">Dan Andersen</reporter>
                        <labels>
                    </labels>
                <created>Mon, 8 Oct 2012 15:52:50 -0500</created>
                <updated>Mon, 11 Feb 2013 14:09:04 -0600</updated>
                    <resolved>Fri, 26 Oct 2012 17:56:13 -0500</resolved>
                            <version>1.0.5</version>
                <version>1.1.0-dp4</version>
                                <fixVersion>1.0.6</fixVersion>
                <fixVersion>1.1.0</fixVersion>
                                <component>library</component>
                                <votes>1</votes>
                        <watches>1</watches>
                                                    <comments>
                    <comment id="40686" author="mnunberg" created="Mon, 8 Oct 2012 15:57:50 -0500"  >For this we&amp;#39;d probably need to change the ext code to return a valid couchbase object so that getResultCode can be called on it (to check for connection failures).&lt;br/&gt;
&lt;br/&gt;
For the non-oo variant (couchbase_connect) behavior should remain the same (?)&lt;br/&gt;
&lt;br/&gt;
Additionally, all the code which now checks for the couchbase object to simply exist should be changed to check that the couchbase object is indeed connected (I believe lcb has a function for that, but if not we can set our own little flag in our php_couchbase_ctx structure).&lt;br/&gt;
&lt;br/&gt;
One workaround is to call set_error_handler and make it throw an ErrorException right before instantiation. Then the connection can be done in a try/catch block, with any message being found in $ex-&amp;gt;getMessage().&lt;br/&gt;
&lt;br/&gt;
I believe there may be ther workarounds as well</comment>
                    <comment id="40799" author="mjackson" created="Tue, 9 Oct 2012 10:25:17 -0500"  >patch set in progress: &lt;a href=&quot;http://review.couchbase.org/#/c/21433/&quot;&gt;http://review.couchbase.org/#/c/21433/&lt;/a&gt;</comment>
                    <comment id="40913" author="mjackson" created="Tue, 9 Oct 2012 19:05:46 -0500"  >As a side note, I have a 1.0.x backport of the changes above ready to roll once the master branch changes are approved/merged.</comment>
                    <comment id="40953" author="mjackson" created="Wed, 10 Oct 2012 10:58:53 -0500"  >master branch changeset is merged in.  1.0.x changeset is here: &lt;a href=&quot;http://review.couchbase.org/#/c/21487/&quot;&gt;http://review.couchbase.org/#/c/21487/&lt;/a&gt;</comment>
                    <comment id="41999" author="mjackson" created="Fri, 19 Oct 2012 18:12:11 -0500"  >(I believe all this needs for resolution is the 1.0.x changeset mentioned above to be merged into 1.0.x branch.)</comment>
                    <comment id="42651" author="mjackson" created="Fri, 26 Oct 2012 17:56:13 -0500"  >1.0.x merged in just now, 1.1 has been in for a bit.  Should be present in next released versions.</comment>
                </comments>
                <issuelinks>
                        <issuelinktype id="10001">
                <name>Duplicate</name>
                                <outwardlinks description="duplicates">
                            <issuelink>
            <issuekey id="16386">PCBC-58</issuekey>
        </issuelink>
                    </outwardlinks>
                                            </issuelinktype>
                    </issuelinks>
                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                                                                                                                                                                    <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>9779</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                                                                    <customfield id="customfield_10181" key="com.atlassian.jira.ext.charting:timeinstatus">
                <customfieldname>Time In Status</customfieldname>
                <customfieldvalues>
                    
                </customfieldvalues>
            </customfield>
                                                </customfields>
    </item>
</channel>
</rss>