![]() Though the actual performance will depend The execution plan that is returned by the server can be used to estimate the Returned, but the query will not be executed. The query and create an execution plan for it. To explain how an AQL query would be executed on the server, the query stringĬan be sent to the server via an HTTP POST request. bindVars (object): key/value pairs representing the bind parameters.The default is false, meaning only the optimal plan will be returned. allPlans: if set to true, all possible execution plans will be returned.Setting this attribute to a low value allows to put aĬap on the amount of work the optimizer does. maxNumberOfPlans: an optional maximum number of plans that the optimizer isĪllowed to generate.There is also a pseudo-rule all, which will match all optimizer rules. To disable a rule, prefix its name with a -, to enable a rule, prefix it les (string): an array of to-be-included or to-be-excluded optimizer rulesĬan be put into this attribute, telling the optimizer to include or exclude.Options for the query can be passed in the options attribute. These must also be passed in the attribute bindVars. query: the query which you want explained If the query references any bind variables,.Explain an AQL queryĮxplain an AQL query and return information about itĪ JSON object describing the query and query parameters.Ī JSON object with these properties is required: Inspect it and return meta information about it. HTTP Interface for AQL Queries Explaining and parsing queriesĪrangoDB has an HTTP interface to syntactically validate AQL queries.įurthermore, it offers an HTTP interface to retrieve the execution plan for anyīoth functionalities do not actually execute the supplied AQL query, but only
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |