<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Tue May 21 11:58:24 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-197/PCBC-197.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-197] different parameter order for incremement</title>
                <link>http://www.couchbase.com/issues/browse/PCBC-197</link>
                <project id="10049" key="PCBC">Couchbase PHP client library</project>
                        <description>From IRC:&lt;br/&gt;
&lt;br/&gt;
lachlan: can the latest php sdk (couchbase.so) still to be a drop in replacement for php memcached?&lt;br/&gt;
[2:39pm] trondn: lachlan: it is supposed to be compatible, but the constructor/factory methods are named differently etc..&lt;br/&gt;
[2:39pm] lachlan: reason I ask is the different order of parameters for increment() between memcached and couchbase sdk&lt;br/&gt;
[2:39pm] lachlan: Memcached::increment ( string $key [, int $offset = 1 [, int $initial_value = 0 [, int $expiry = 0 ]]] )&lt;br/&gt;
[2:39pm] lachlan: Couchbase - $object-&amp;gt;increment($key [, $offset ] [, $create ] [, $expiry ] [, $initial ])&lt;br/&gt;
[2:39pm] trondn: hmm.. I guess that&amp;#39;s a bug...&lt;br/&gt;
[2:40pm] trondn: let me file that one...&lt;br/&gt;
[2:40pm]</description>
                <environment></environment>
            <key id="22541">PCBC-197</key>
            <summary>different parameter order for incremement</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="1" iconUrl="http://www.couchbase.com/issues/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                    <security id="10011">Public</security>
                        <assignee username="ingenthr">Matt Ingenthron</assignee>
                                <reporter username="trond">Trond Norbye</reporter>
                        <labels>
                    </labels>
                <created>Tue, 5 Feb 2013 16:41:24 -0600</created>
                <updated>Tue, 16 Apr 2013 03:50:21 -0500</updated>
                                                                                    <votes>0</votes>
                        <watches>1</watches>
                                                    <comments>
                    <comment id="55124" author="trond" created="Tue, 16 Apr 2013 03:46:19 -0500"  >This will result in an API breakage... What should we do?</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                                                                                                                                                                    <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>8535</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                                                                                            </customfields>
    </item>
</channel>
</rss>