mirror of https://gitee.com/bigwinds/arangodb
documented WITH change
This commit is contained in:
parent
7040ea72fa
commit
5c464301b2
|
@ -20,6 +20,9 @@ However, if client applications specify the list of used collections for all
|
|||
their queries using *WITH*, then no deadlocks will happen and no queries will
|
||||
be aborted due to deadlock situations.
|
||||
|
||||
From ArangoDB 3.1 onwards `WITH` is required for traversals in a
|
||||
clustered environment in order to avoid deadlocks.
|
||||
|
||||
Note that for queries that access only a single collection or that have all
|
||||
collection names specified somewhere else in the query string, there is no
|
||||
need to use *WITH*. *WITH* is only useful when the AQL query parser cannot
|
||||
|
|
|
@ -47,6 +47,8 @@ The behavior of the AQL array comparison operators has changed for empty arrays:
|
|||
* `[1, 2] NONE == 1` will return `false`
|
||||
* `[2, 2] NONE == 1` will return `true`
|
||||
|
||||
* `WITH` in cluster traversals is now mandatory in order to avoid deadlocks.
|
||||
|
||||
Data format changes
|
||||
-------------------
|
||||
|
||||
|
|
Loading…
Reference in New Issue