14 Commits

Author	SHA1	Message	Date
Max Neunhoeffer	4451e491ec	Merge branch 'devel' into ClustUp1	2015-12-15 17:46:34 +01:00
Alan Plum	8853ede355	org/arangodb -> @arangodb	2015-12-15 15:51:44 +01:00
Max Neunhoeffer	ea72850aeb	Fix bug in client tests.	2015-12-09 23:13:26 +01:00
Alan Plum	69e63c2c64	Strict mode all the things.	2015-04-09 00:22:05 +02:00
Willi Goesgens	ace14bb257	lintify the common testsuite. This should reduce our valgrind false positives.	2015-02-04 20:06:33 +01:00
Jan Steemann	36dab4113e	stricter checking for AQL user functions	2015-01-16 12:44:59 +01:00
Jan Steemann	ef1f56c42c	added tests	2015-01-16 12:34:11 +01:00
Alan Plum	606da1e3e8	Removed jslint headers from server/client/common modules.	2014-09-02 22:14:56 +02:00
Jan Steemann	7a3635adf9	fixed problem with AQL functions in multiple databases	2014-01-08 09:53:03 +01:00
Jan Steemann	9bb89bb654	fixed "error with AQL in user function"	2013-10-16 09:43:24 +02:00
Jan Steemann	e359dc29dd	INCOMPATIBLE CHANGE: changed AQL user function namespace resolution operator from `:` to `::` ... 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.	2013-07-18 12:02:28 +02:00
Jan Steemann	ede177aa55	issue #507, issue #508	2013-05-06 09:40:28 +02:00
Jan Steemann	7d9777f8c5	extended API for user-defined AQL functions	2013-04-16 18:32:19 +02:00
Jan Steemann	ed10d9b6aa	AQL user functions	2013-04-05 12:50:44 +02:00