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

Merge branch 'devel' of github.com:triAGENS/ArangoDB into devel

This commit is contained in:
Heiko Kernbach 2014-11-07 14:49:50 +01:00
parent 10368540ad 7618d03a10
commit 76e95227a0
1 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
Documentation/Books/Users/Upgrading/UpgradingChanges23.mdpp
View File

@ -143,13 +143,20 @@ will look like this:
} }
``` ```
If the query option `fullCount` is requested, the `fullCount` result value will also
be returned inside the `stats` attribute of the `extra` attribute, and not directly
as an attribute inside the `extra` attribute as in 2.2. Note that a `fullCount` will
only be present in `extra`.`stats` if it was requested as an option for the query.
The result in ArangoDB 2.3 will also contain a `warnings` attribute with the list of The result in ArangoDB 2.3 will also contain a `warnings` attribute with the list of
warnings that happened during query execution. warnings that happened during query execution.
!SUBSECTION Changed return values in ArangoStatement.explain() !SUBSECTION Changed return values in ArangoStatement.explain()
The return value of `ArangoStatement.explain()` has been changed in ArangoDB 2.3. The return value of `ArangoStatement.explain()` has changed significantly in
ArangoDB 2.3. The new return value structure is not compatible with the structure
returned by 2.2.
In ArangoDB 2.3, the full execution plan for an AQL query is returned alongside all In ArangoDB 2.3, the full execution plan for an AQL query is returned alongside all
applied optimizer rules, optimization warnings etc. It is also possible to have the applied optimizer rules, optimization warnings etc. It is also possible to have the