[PCBC-197] different parameter order for incremement Created: 05/Feb/13 Updated: 16/Apr/13 |
|
| Status: | Open |
| Project: | Couchbase PHP client library |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Security Level: | Public |
| Type: | Bug | Priority: | Major |
| Reporter: | Trond Norbye | Assignee: | Matt Ingenthron |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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] |
| Comments |
| Comment by Trond Norbye [ 16/Apr/13 ] |
| This will result in an API breakage... What should we do? |