In ArangoDB, the query will still be executed to completion and continue toĬonsume resources in the database or cluster. Simply close the connection and not result in the actual query being cancelled Request to be cancelled after that amount of milliseconds.
Note: Dirty reads were introduced in ArangoDB 3.4 and are not supported by earlierĪdditionally opts.timeout can be set to a non-negative number to force the not using INSERT, UPDATE, REPLACE or REMOVE expressions). Note that dirty reads are only supported for read-only queries Possible key options in opts.options include: failOnWarning, cache,įor a complete list of query settings please reference theĪdditionally if opts.allowDirtyRead is set to true, the request willĮxplicitly permit ArangoDB to return a potentially dirty or stale result andĪrangojs will load balance the request without distinguishing between leadersĪnd followers.
If unt is set to true, the cursor will have a count property set to Possible keys are count and options (explained below) If the query is an AQL query object, the second argument is treated as theĪn object defining the variables to bind the query to.Īdditional parameter object that will be passed to the query API. Performs a database query using the given query and bindVars, then returns a database.queryĪsync database.query(query, ): Cursor HTTP API for single round-trip AQL queriesįor collection-specific queries see Simple Queries. Queries The official ArangoDB JavaScript driver.
0 kommentar(er)
