index or (#148)

vesoft-inc · Sep 23, 2020 · 52b51d1 · 52b51d1
1 parent c0c0350
commit 52b51d1
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/...ge/4.statement-syntax/2.data-query-and-manipulation-statements/lookup-syntax.md b/...ge/4.statement-syntax/2.data-query-and-manipulation-statements/lookup-syntax.md
@@ -12,7 +12,7 @@ LOOKUP ON {<vertex_tag> | <edge_type>} WHERE <expression> [ AND | OR expression
 ```
 
 - `LOOKUP` clause finds the vertices or edges.
-- `WHERE` extracts only those results that fulfill the specified conditions. The logical AND is also supported. See [WHERE Syntax](where-syntax.md) for more information.
+- `WHERE` extracts only those results that fulfill the specified conditions. Only logical AND is supported. See [WHERE Syntax](where-syntax.md) for more information.
 - `YIELD` clause returns particular results. If not specified, vertex ID is returned when `LOOKUP` tags, source vertex ID, destination vertex ID and ranking of the edges are returned when `LOOKUP` edges.
 
 ## Restrictions for index usage
@@ -23,6 +23,7 @@ The `WHERE` clause does not support the following operations in `LOOKUP`:
 - In relational expressions, expressions with field-names on both sides of the operator are not currently supported, such as (tagName.column1> tagName.column2)
 - Nested AliasProp expressions in operation expressions and function expressions are not supported at this time.
 - Range scan is not supported in the string type index.
+- The `OR` and the `OXR` operations are not supported.
 
 ## Retrieve Vertices