7 Commits

Author	SHA1	Message	Date
Jan	5ce22a3bc9	make API for POST /_api/aqlfunction downwards-compatible again (#5636)	2018-06-20 12:52:54 +02:00
Wilfried Goesgens	619155a62d	Feature/aqlfunction to cpp (#4573)	2018-02-13 11:50:49 +01:00
Jan Steemann	34c3ac0f56	fixed incompatibilies with newer rspec/ruby versions ... Conflicts: UnitTests/HttpInterface/api-collection-spec.rb	2015-01-16 12:34:12 +01:00
Max Neunhoeffer	3d332ad01e	Adjust paths to allow call with a different current dir.	2014-02-20 10:20:24 +01: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