I understand that we can build the master manually for the fix, but don’t you think March is a little bit late?
This is obviously a bug for a major feature in Couchbase 4 and the fix is really really easy. It’s one character change. I don’t really understand the decision behind March release. This is perfectly fine for a minor update in my opinion.
We’ve been in the process of updating a few things on build and test infrastructure @moon0326 and we wanted to have that in place for the next release. Indeed, a one character change is seemingly simple but we’d also had a couple of other larger changes planned for the release that need the full build/test infrastructure.
Maybe to get you unblocked, we can put together a build from what’s being worked on for the March release and you can verify that it relieves the issues for you? What PHP version, and OS are you looking for?
I don’t know if you’ve worked with PECL extensions before, but between the varying platforms and versions, we run into situations where something that seems like an obvious fix on one version of PHP 5.x won’t work on another platform.
I understand that there is a release schedule/plan. My only complaint was that n1ql is such a major feature in Couchbase 4 and It is a little bit let down that I can’t even use n1ql correctly with PHP SDK that was released months ago just because there was no test for the SDK to check a mistake.
I decided to hack around it. I think I’m good for now. Below is the new query method I’m using.
This is quite a clever workaround, a bit of a hack, but definitely clever. Note that a possible ‘simpler’ workaround would be to use the query method itself and then simply wrap the results to re-encode. For instance:
It is already mid April and I don’t think there is a new release that fixes the problem discussed in this thread.
Couchbase 4.5 DP is out with bunch of new features including new additions for n1ql.
I don’t understand how this little, but important bug cannot be fixed after 2 months+. Couchbase has been pushing n1ql forward and yet…PHP users cannot even use the most basic feature without hacking around the official SDK.
I agree it’s a small change. That said, there is a workaround (you documented it!) and the branch had other changes in it that needed testing. Our new testing necessitated changes in our build infrastructure. The good news is that all of that is done now and we’re moving forward on our next update which will have this fix and a number of others.
The process we have, which has worked for us, is to have a regular cadence of releases that roll up fixes so we can test it well, update docs regularly, etc. We’re behind on PHP, but going to catch up.