mirror of https://gitee.com/bigwinds/arangodb
Minor corrections
This commit is contained in:
parent
98423f451e
commit
097dcb0984
10
CHANGELOG
10
CHANGELOG
|
@ -4,13 +4,13 @@ v3.0.0 (XXXX-XX-XX)
|
|||
* make AQL optimizer rule "remove-unnecessary-calculations" fire in more cases
|
||||
|
||||
The rule will now remove calculations that are used exactly once in other
|
||||
expressions (e.g. `LET a = doc RETURN a.value`) and calculations
|
||||
expressions (e.g. `LET a = doc RETURN a.value`) and calculations,
|
||||
or calculations that are just references (e.g. `LET a = b`).
|
||||
|
||||
* renamed AQL optimizer rule "merge-traversal-filter" to "optimize-traversals"
|
||||
Additionally, the optimizer rule will remove unused edge and paths result variables
|
||||
Additionally, the optimizer rule will remove unused edge and path result variables
|
||||
from the traversal in case they are specified in the `FOR` section of the traversal,
|
||||
but are not referenced later in the query. This saves constructing edges and paths
|
||||
but not referenced later in the query. This saves constructing edges and paths
|
||||
results.
|
||||
|
||||
* added AQL optimizer rule "inline-subqueries"
|
||||
|
@ -39,8 +39,8 @@ v3.0.0 (XXXX-XX-XX)
|
|||
|
||||
* The result order of the AQL functions VALUES and KEYS has never been guaranteed
|
||||
and it only had the "correct" ordering by accident when iterating over objects that
|
||||
were not loaded from the database. This behaviour is now changed by
|
||||
introduction of VelocyPack and no ordering is guaranteed unless you specify
|
||||
were not loaded from the database. This accidental behavior is now changed by
|
||||
introduction of VelocyPack. No ordering is guaranteed unless you specify
|
||||
the sort parameter.
|
||||
|
||||
* removed configure option `--enable-logger`
|
||||
|
|
|
@ -59,7 +59,7 @@ void Aqlerror (YYLTYPE* locp,
|
|||
}
|
||||
|
||||
////////////////////////////////////////////////////////////////////////////////
|
||||
/// @brief check if any of variables used into the INTO expression was
|
||||
/// @brief check if any of the variables used in the INTO expression were
|
||||
/// introduced by the COLLECT itself, in which case it would fail
|
||||
////////////////////////////////////////////////////////////////////////////////
|
||||
|
||||
|
|
|
@ -71,7 +71,7 @@ typedef uint32_t TRI_fulltext_handle_t;
|
|||
/// to documents are just adjacent (second pointer is higher than first
|
||||
/// pointer).
|
||||
/// This is only true for documents that are created on the same memory page
|
||||
/// but this should be the common case to optimise for.
|
||||
/// but this should be the common case to optimize for.
|
||||
////////////////////////////////////////////////////////////////////////////////
|
||||
|
||||
typedef struct TRI_fulltext_handle_slot_s {
|
||||
|
|
Loading…
Reference in New Issue