Is Wording Confusing?

In Mobile Android Java Docs under Indexing:
"If there are multiple expressions, the first one will be the primary key, the second the secondary key, etc."

In Traditional Database, a Primary Key must be a unique for each record. If the syntax being described is actually analogous to Composite Indexes there would be no such constraint.

Personally, I usually say leading attribute to indicate the first JSON attribute (since the word "key" is used in so many contexts that it routinely confuses people.) So I always speak of JSON properties as attribute-value pairs. And in Traditional Database terms the entire data structure is a Secondary Index, so talking about a "secondary key" is doubly confusing.

Reporter: Tony Duarte
E-mail: tony.duarte@couchbase.com