Skip to content

Commit 200d7ad

Browse files
committed
flex-indexes.adoc small corrections (couchbase/docs-server#2699)
Correct array example and hint
1 parent 2eaddf0 commit 200d7ad

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

modules/n1ql/pages/n1ql-language-reference/flex-indexes.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ Some of the main differences are described here.
5858

5959
* {sqlpp} uses escaped path names, whereas full-text indexes flatten the field names.
6060

61-
* {sqlpp} uses array subscripts to identify array objects, for example `1.arr1[0].b`; whereas full-text indexes ignore subscripts, for example `f1.arr1.b`.
61+
* {sqlpp} uses array subscripts to identify array objects, for example `f1.arr1[0].b`; whereas full-text indexes ignore subscripts, for example `f1.arr1.b`.
6262
This means full-text indexes cannot uniquely identify the path.
6363

6464
* In {sqlpp}, data can be compared across data types.
@@ -94,7 +94,7 @@ For further details, refer to {build-index}[BUILD INDEX].
9494

9595
Assuming that there is no search function in the query predicate, there are two ways to specify that you would like to use a full-text index with a {sqlpp} query:
9696

97-
* Use the `USE FTS` hint in the {sqlpp} query.
97+
* Use the `USING FTS` hint in the {sqlpp} query.
9898
For full details, refer to {index-type}[USE Clause].
9999

100100
* Set the `use_fts` request-level parameter to `true`.

0 commit comments

Comments
 (0)