What i’m trying to do is to query the bucket ‘default’ with this query “SELECT META().id, file FROM default WHERE META().id LIKE ‘file_’|| $name ||’%”
In python the line looks like res = bucket.query(“SELECT META().id, file FROM default WHERE META().id LIKE ‘file_’|| $name ||’%’”, name=“128794”) (currently passing a hard coded value to comfirm the bug, it’s still there).
This should work as to my understanding, but it’s throwing an exception with the error msg “Error evaluating filter. - cause: No value for named parameter $name”
The 3.0 sdk expects you to issue queries from the cluster object rather than the bucket. However, since the bucket, collection and cluster share a base class (which has a query function in it), that leaks out and could be used. The sdk3 n1ql docs have some examples of how to make queries now. But, basically you do cluster.query(query_string, name=“128794”) and you are all set.
Agreed on tightening up exposed functions - I was already working on some refactoring so vestigial functionality is removed/hidden, and not just in the API docs. Hopefully will get this in to the codebase soon.