| options |
Options with which to customize this operation.
You can specify options as either an options XML element
in the namespace "xdmp:eval", or as a map:map. The
option names below are XML localnames. When using a map, replace any
hyphens in an option name with camel casing. For example, "an-option"
becomes "anOption" when used as a map:map entry key.
This function supports the following options:
- database
- The id of the content database. You can use functions such
as
xdmp:database
to get a database ID.
See the Usage Notes for more details. Use of this option to specify
a database other than the context database requires additional
privileges. For details, see Required Privileges, below.
- modules
- The ID of the modules database to use for resolving module imports.
If you do not specify a
modules option, this operation
uses the current modules database. Use a value of 0 to
specify using the file system to resolve module imports. Use of this
option to specify a modules database other than the one configured
for the App Server requires additional privileges. For details, see
Required Privileges, below.
- root
- The root path for modules. If you do not explicitly specify a
root option, the current root is used. Use of this
option to specify a root path other than the one configured for the
App Server requires additional privileges. For details, see
Required Privileges, below.
- timestamp
- The system timestamp to use for this evaluation. If you omit this
option, the most recent timestamp is used. You may only specify a
timestamp for a query statement, not for an update statement. Use a
value of zero to specify the current system timestamp (the value that
would be returned by
xdmp:request-timestamp
).
For more details see
Understanding Point-In-Time Queries.
Use of this option requires additional privileges. For
details, see Required Privileges, below.
- ignore-amps
-
Whether or not to evaluate the code without using any Amps from the caller.
Allowed values: true, false (default). If this option is set to
true, the code is evaluated without using Amps from the
caller. For more details, see
Temporarily Increasing Privileges with Amps.
You cannot use this option with dbg:eval.
- isolate
-
Whether or not to evaluate the code with the calling HTTP request,
HTTP response, and session context hidden from the evaluated code.
Allowed values: true, false (default). If this option is set to
true, the evaluated code runs as if outside of an HTTP
App Server: builtins that read request headers, cookies, or
authorization credentials, or that write response headers, status, or
content type (such as
xdmp:get-request-header
and
xdmp:add-response-header),
behave as if called outside of an HTTP context (typically returning
the empty sequence). Session-related builtins likewise have no session
to read or update; in particular,
xdmp:set-session-field
returns the set value instead of creating a new session.
This option is intended as a defense-in-depth control when executing
user-supplied code, and is typically used together with
ignore-amps. This option is not usable with dbg:eval.
- isolation
- Specify the transaction isolation for this operation. Allowed values:
same-statement, different-transaction (default).
When set to same-statement, the evaluation occurs in the
same transaction in which this function is called. When set to
different-transaction, the evaluation occurs in a separate
transaction from the one in which this function is called. If you use
same-statement isolation in a query (read-only) statement
and the eval'd code attempts an update, MarkLogic throws the exception
XDMP-UPDATEFUNCTIONFROMQUERY. For more details, see
Isolation Option to xdmp:eval/invoke.
- commit
-
The commit mode for the transaction in which the code is evaluated.
Allowed values:
auto (default), explicit.
In auto mode, a transaction is committed for every statement.
In explicit mode, the transaction must be explicitely
committed or rolled back. For more details, see
Commit Mode.
- update
-
Specify the transaction type in which to evaluate this code, or let
MarkLogic determine the transaction type. Allowed values:
"true", "false", "auto" (default).
For more details, see
Transaction Type Overview.
- static-check
-
Whether or not to only perform a static analysis of the code, without
executing it. Allowed values:
true, false
(default).
- prevent-deadlocks
-
Whether or not to disallow update requests from an update transaction.
Allowed values:
true, false (default). This
option only has an effect when you set the isolation option
to different-transaction since there is no possibility of
deadlock if the isolation is same-statement. When you set
this option to true in an update request calling another
update request, MarkLogic throws the exception
XDMP-PREVENTDEADLOCKS. Setting this option to
true prevents deadlocks from occurring when evaluating
or invoking an update transaction from another update transaction.
For more details, see
Preventing Deadlocks.
- default-xquery-version
- The default XQuery language version to use for the query, if the query
does not contain an explicit version declaration. If this option is not
provided, then MarkLogic uses the default XQuery version for the
App Server that called this function. The version may vary from module
to module if a query consists of modules written in multiple XQuery
versions. If may also var from run to run if the App Server default
changes across runs.
Allowable values for this option are "0.9-ml", "1.0-ml", "1.0", and
the special value "app-server". The first three are XQuery language
versions. The last indicates that the default XQuery language
version set on this App Server should be used. This is useful if code
written in an older XQuery version needs to call this function
on strings that may have been passed as parameters, but should be
interpreted in the App Server default language version. A module
can discover its own XQuery language version with
xdmp:xquery-version()
.
- user-id
- The ID of the user under which this operation should be performed.
If you do not set this option, the operation is performed as the
current user. Use of htis option requires additional privileges. For
details, see Required Privileges, below. NOTE: This is a very
privileged operation since it enables a user to evaluate requests as
any other user. For an example, see the
fourth example below.
- default-collation
- Specifies the collation to use for this operation if a collation
is not explicitly specified, such as in the XQuery prolog or in a
function call that allows you to specify a collation. For more
details, see
Encodings and Collations.
- default-coordinate-system
- Specifies the geospatial coordinate system to use for this operation,
if a coordinate system is not explicitly specified, such as in the XQuery prolog
or in a function call that allows you to specify a coordinate system.
For more details, see
Controlling Coordinate System and Precision and
Supported Coordinate Systems.
- transaction-mode
- [DEPRECATED: Use the
update and commit
options instead.] Explicitly set the transaction mode for this context.
Allowed values: auto (default), query,
update-auto-commit, update. For details, see
Transaction Mode.
For simple updates to be implicitly committed, specify a transaction
mode of update-auto-commit. A transaction mode of
update creates a new multi-statement update
transaction and requires an explicit commit in the code.
Within a session there can be only one active multi-statement
transaction at a time. If a new multi-statement transaction is
specified nested inside a multi-statement transaction, MarkLogic throws
the exception XDMP-NESTEDMULTI. If a new multi-statement
transaction is specified after another has been concurrently created
in the same session by another request, MarkLogic throws the exception
XDMP-SESSIONTXN and retries the current request.
An xdmp:transaction-mode XQuery prolog
option in the evaluated code overrides any transaction mode specified
with this option.
|