MarkLogic 12 EA 2 Product Documentation
xdmp:javascript-evalxdmp:javascript-eval(
$javascript as xs:string,
[$vars as item()* | map:map],
[$options as (node()? | map:map)?]
) as item()*
Summary
Returns the result of evaluating a string as a JavaScript module.
To evaluate XQuery, see xdmp:eval.
Parameters |
javascript |
A string containing JavaScript code to be evaluated.
The JavaScript string to be evaluated. If the JavaScript string contains
single quotes ('), surround the string with double quotes (").
|
vars |
External variable values to make available to the evaluated code,
expressed as either a sequence of alternating variable name-value pairs,
or a map:map . If you use a sequence, it must contain
alternating variable names and values. e.g.
("var1", "val1", "var2", "val2").
If you use a map, then each map entry has a key corresponding to the
variable name and a value corresponding to the variable value.
|
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. Using this option
may require 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. Using this
option may require 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 may require 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 ). Use of this
option requires the privilege
http://marklogic.com/xdmp/privileges/xdmp-timestamp
For more details see
Understanding Point-In-Time Queries in the Application Developer's Guide.
- 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 in the Security Guide.
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 in the Application Developer's Guide.
- 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 in the Application Developer's Guide.
- 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 in the Application Developer's Guide.
- 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 in the Application Developer's Guide.
- 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 this option requires additional privileges. For
details, see Required Privileges, below. NOTE: This is a very
privileged operation since it enables a user to
to evaluate requests as any other user.
- 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 in the Search Developer's Guide.
- 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 in the Search Developer's Guide and
Supported Coordinate Systems in the Search Developer's Guide.
- 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 in the Application Developer's Guide.
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.
|
Required Privileges
To use this function, you must have the following privilege:
http://marklogic.com/xdmp/privileges/xdmp-eval
To use the database
option to specify a content database
other than the default database for the current App Server, you must
have the following privilege:
http://marklogic.com/xdmp/privileges/xdmp-eval-in
To use the modules
or root
options to specify
to specify a modules database or root other than that configured for the
current App Server, you must have the following privilege:
http://marklogic.com/xdmp/privileges/xdmp-eval-modules-change
To use the modules
or root
options to specify
to specify using the file system as the modules database or root path, you
you must have the following privilege:
http://marklogic.com/xdmp/privileges/xdmp-eval-modules-change-file
To use the user-id
option, you must have the
following privilege:
http://marklogic.com/xdmp/privileges/xdmp-login
To use the timestamp
option, you must have the following
privileges:
http://marklogic.com/xdmp/privileges/xdmp-timestamp
Usage Notes
To get the database ID for options that require one, such as
the database
or modules
options, you can use
functions such as the following. Use the function appropriate to the
database you want to reference.
See Also
Example
xdmp:javascript-eval("1+1")
=> 2
Example
let $foo :=
'var mycars = xdmp.arrayValues(["Saab","Volvo","BMW","BMW"]);
fn.distinctValues(mycars);'
return
xdmp:javascript-eval($foo)
=> Saab,Volvo,BMW
Example
xdmp:javascript-eval("fn.doc('/docs/mydoc.xml')", (),
<options xmlns="xdmp:eval">
<database>{xdmp:database("otherdb")}</database>
</options>)
=> The '/docs/mydoc.xml' document from the
otherdb database.
Example
xdmp:javascript-eval('xdmp.getCurrentUser()', (),
<options xmlns="xdmp:eval">
<user-id>{xdmp:user("someuser")}</user-id>
</options>)
(:
returns "someuser", assuming "someuser" exists in the
security database and the user running the eval request has the
xdmp:login privilege.
:)
Example
let $s := "var h; var w; xdmp.log(h+' '+w);"
return
xdmp:javascript-eval($s,("h","hello","w","world"))
(:
logs "hello world" in ErrorLog.
:)
Stack Overflow: Get the most useful answers to questions from the MarkLogic community, or ask your own question.