Hawkin
/
arangodb
mirror of https://gitee.com/bigwinds/arangodb
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

documented WITH change

This commit is contained in:
Frank Celler 2017-05-25 23:00:24 +02:00
parent 7040ea72fa
commit 5c464301b2
2 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Documentation/Books/AQL/Operations/With.md
View File

@ -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 their queries using *WITH*, then no deadlocks will happen and no queries will
be aborted due to deadlock situations. 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 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 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 need to use *WITH*. *WITH* is only useful when the AQL query parser cannot

2
Documentation/Books/Manual/ReleaseNotes/UpgradingChanges31.md
View File

@ -47,6 +47,8 @@ The behavior of the AQL array comparison operators has changed for empty arrays:
* `[1, 2] NONE == 1` will return `false` * `[1, 2] NONE == 1` will return `false`
* `[2, 2] NONE == 1` will return `true` * `[2, 2] NONE == 1` will return `true`
* `WITH` in cluster traversals is now mandatory in order to avoid deadlocks.
Data format changes Data format changes
------------------- -------------------