Browsing an un-indexed Couchbase collection
On recent server versions a sequential scan makes an un-indexed keyspace open slowly, so a primary index is a recommendation now rather than a prerequisite.
6 posts
Writing on Couchbase
SQL++ queries with bucket, scope and collection introspection over the documented REST surfaces. Where it stops: Agent mode is unavailable, as on every engine but PostgreSQL, SQLite and DuckDB.
Writing SQL++ that starts with the document key
Selecting everything nests the document and drops the key, so generated statements project it explicitly, and that alias is why cell editing is switched off.
Couchbase plan trees are estimates, and minus one means none
This dialect has no analyze form, so the direct action and the background pre-warm show the same estimate, and a negative cost renders as no estimate.
The Couchbase role your monitoring panels depend on
Without the query system catalog role, slow queries and sessions are empty and denied metrics are omitted rather than reported as zero.
Connecting to Couchbase Capella and the bucket you type in
A managed endpoint carries neither a port nor a bucket path, so the scheme supplies the port and the TLS mode while the bucket is typed by hand and nothing is invented for it.
You configure the management port, the query port is discovered
Only the management port is stored, and the query endpoint comes from the cluster's own node services, preferring the external address it advertises.