mirror of https://gitee.com/bigwinds/arangodb
e359dc29dd
AQL user-defined functions were introduced in ArangoDB 1.3, and the namespace resolution
operator for them was the single colon (`:`). A function call looked like this:
RETURN mygroup:myfunc()
The single colon caused an ambiguity in the AQL grammar, making it indistinguishable from
named attributes or the ternary operator in some cases, e.g.
{ mygroup:myfunc ? mygroup:myfunc }
The change of the namespace resolution operator from `:` to `::` fixes this ambiguity.
Existing user functions in the database will be automatically fixed when starting ArangoDB
1.4 with the `--upgrade` option. However, queries using user-defined functions need to be
adjusted on the client side to use the new operator.
|
||
|---|---|---|
| .. | ||
| Cambridge | ||
| HttpInterface | ||
| Jutland | ||
| Philadelphia | ||
| Makefile.unittests | ||
| Runner.cpp | ||
| import-1.csv | ||
| import-1.json | ||
| import-1.tsv | ||
| import-2.csv | ||
| import-2.json | ||
| import-2.tsv | ||
| import-3.json | ||
| import-4.json | ||
| import-edges.json | ||
| server.pem | ||