Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Security Level: Public
    • Labels:
      None

      Description

      From IRC:

      lachlan: can the latest php sdk (couchbase.so) still to be a drop in replacement for php memcached?
      [2:39pm] trondn: lachlan: it is supposed to be compatible, but the constructor/factory methods are named differently etc..
      [2:39pm] lachlan: reason I ask is the different order of parameters for increment() between memcached and couchbase sdk
      [2:39pm] lachlan: Memcached::increment ( string $key [, int $offset = 1 [, int $initial_value = 0 [, int $expiry = 0 ]]] )
      [2:39pm] lachlan: Couchbase - $object->increment($key [, $offset ] [, $create ] [, $expiry ] [, $initial ])
      [2:39pm] trondn: hmm.. I guess that's a bug...
      [2:40pm] trondn: let me file that one...
      [2:40pm]

      No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

        Hide
        trond Trond Norbye added a comment -

        This will result in an API breakage... What should we do?

        Show
        trond Trond Norbye added a comment - This will result in an API breakage... What should we do?
        Hide
        ingenthr Matt Ingenthron added a comment -

        Brett: can you evaluate what we should do here?

        Note that there is pecl/memcache and pecl/memcached. We've sort of copied the later and try to be somewhat API compatible, though there are clearly some constructor and error handling differences.

        Show
        ingenthr Matt Ingenthron added a comment - Brett: can you evaluate what we should do here? Note that there is pecl/memcache and pecl/memcached. We've sort of copied the later and try to be somewhat API compatible, though there are clearly some constructor and error handling differences.
        Hide
        trond Trond Norbye added a comment -

        Changing the API will cause problems from others thats already using it :S

        Show
        trond Trond Norbye added a comment - Changing the API will cause problems from others thats already using it :S
        Hide
        brett19 Brett Lawson added a comment -

        I don't think changing this at this point is the best options, it will just confuse our existing users as Trond said. I think this is going to be something that was err'd on when the API was developed, that we may have to live with RFC!

        Show
        brett19 Brett Lawson added a comment - I don't think changing this at this point is the best options, it will just confuse our existing users as Trond said. I think this is going to be something that was err'd on when the API was developed, that we may have to live with RFC!

          People

          • Assignee:
            brett19 Brett Lawson
            Reporter:
            trond Trond Norbye
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes