For this we'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).
For the non-oo variant (couchbase_connect) behavior should remain the same (?)
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).
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->getMessage().
I believe there may be ther workarounds as well
|
|
patch set in progress: http://review.couchbase.org/#/c/21433/
|
|
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.
|
|
master branch changeset is merged in. 1.0.x changeset is here: http://review.couchbase.org/#/c/21487/
|
|
(I believe all this needs for resolution is the 1.0.x changeset mentioned above to be merged into 1.0.x branch.)
|
|
1.0.x merged in just now, 1.1 has been in for a bit. Should be present in next released versions.
|
Generated at Fri May 24 11:45:17 CDT 2013 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.