1
0
Fork 0

Merge pull request #1616 from kibarda/devel

documentation: point out the User Function is defined on the selected database
This commit is contained in:
Jan 2015-12-16 22:39:30 +01:00
commit c4f5f69b01
3 changed files with 8 additions and 7 deletions

View File

@ -82,7 +82,8 @@ to undefined behavior and should be avoided.
!SECTION Miscellaneous !SECTION Miscellaneous
Internally, user functions are stored in a system collection named Internally, user functions are stored in a system collection named
*_aqlfunctions*. That means that by default they are excluded from dumps *_aqlfunctions* of the selected database.
That means that by default they are excluded from dumps
created with [arangodump](../HttpBulkImports/Arangodump.md). created with [arangodump](../HttpBulkImports/Arangodump.md).
To include AQL user functions in a dump, the dump should be started To include AQL user functions in a dump, the dump should be started
with the option *--include-system-collections true*. with the option *--include-system-collections true*.

View File

@ -1,7 +1,7 @@
!CHAPTER Registering and Unregistering User Functions !CHAPTER Registering and Unregistering User Functions
AQL user functions can be registered using the *aqlfunctions* object as AQL user functions can be registered in the selected database
follows: using the *aqlfunctions* object as follows:
```js ```js
var aqlfunctions = require("@arangodb/aql/functions"); var aqlfunctions = require("@arangodb/aql/functions");

View File

@ -4,9 +4,9 @@ AQL comes with a built-in set of functions, but it is not a
fully-featured programming language. fully-featured programming language.
To add missing functionality or to simplify queries, users To add missing functionality or to simplify queries, users
may add their own functions to AQL. These functions can be written may add their own functions to AQL in the selected database.
in JavaScript, and must be registered via the API; These functions can be written in JavaScript, and must be
see [Registering Functions](../AqlExtending/Functions.md). registered via the API; see [Registering Functions](../AqlExtending/Functions.md).
In order to avoid conflicts with existing or future built-in In order to avoid conflicts with existing or future built-in
function names, all user functions must be put into separate function names, all user functions must be put into separate