Couchbase-lite-2.0 IOS - Querying is not generic anymore.

query
#21

For what it’s worth from me, I do see the value of a string based query language. The problem is that there are no lexer parser engines out there that understand N1QL except for the ones in Couchbase Server which are written in Go which are unusable in a mobile SDK. We’d basically be starting over on a project that has been in development for 3 years so it would definitely not happen overnight and after that it depends on the demand for it in the end. We’ll have to see what becomes of it. There is nothing in the current SDK or Couchbase Server that will help us except for docs and possibly grammar rules that could be analyzed and applied. NSPredicate does not count because that leaves the other SDK platforms high and dry.

Personally I also find the query builder easy to understand because it is similar to another concept in C# called LINQ and I work on the C# SDK for mobile. It’s just a bit verbose is the thing.

#22

Thanks for that response. Understood. I’ve built a lot of stuff with both .NET/LINQ and Go. Chalk it up as a +1 for string query support API, FWIW, but I understand the constraints. Thanks for the explanation.

#23

@priya.rajagopal For tracking, another request for string based query.

#24

For the record, I’m in favor of having a JSON API, as infrastructure for alternative ways of creating queries.

One of the reasons we went with a strongly-typed API was support costs. The experience of the server support engineers is that ‘trivial’ errors in N1QL syntax are the cause of a surprisingly large number of support requests.