Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: None
-
Fix Version/s: 1.0
-
Component/s: None
-
Security Level: Public
-
Labels:None
Description
via http://www.couchbase.com/forums/thread/undefined-class-constant-resnotfound
we not returning libmemcached compatible status codes.
I'm not sure what the right thing is here. Using libcouchbase's sounds like the right thing to do going forward, but it also breaks BC.
We could make PCBC implement libmemcached's constants, but then we are stuck there forever.
What's a good way forward?
we not returning libmemcached compatible status codes.
I'm not sure what the right thing is here. Using libcouchbase's sounds like the right thing to do going forward, but it also breaks BC.
We could make PCBC implement libmemcached's constants, but then we are stuck there forever.
What's a good way forward?
Activity
- All
- Comments
- Work Log
- History
- Activity
- Gerrit Reviews
1. Do not implement libmemcached-style constants.
2. Create a "migration guide" that documents all the differences (there are more than just the constants) and how to shows examples on how to migrate existing code.
3. Profit.
I'm tracking this in
PCBC-39.Let me know if you disagree! :)