MarkLogic debugger has the following peculiarities and limitations:
- Debugging support is available only for MarkLogic server versions 3.2 or newer.
- For MarkLogic server versions 4.0 or newer there are three XQuery syntaxes which are
supported: '0.9-ml' (inherited from MarkLogic 3.2), '1.0-ml' and '1.0'
- All the debugging steps are executed by the MarkLogic server and the results or possible
errors of each step are presented by the local debugger user interface.
- All declared variables are presented as strings. The Value column
of the Variables view contains the expression from the variable
declaration. It can be evaluated by copying the expression with the Copy
value action from the contextual menu of the
Variables view and pasting it in the
XWatch view.
- No support for Output to
Source Mapping.
- No support for showing the trace.
- Breakpoints can be set in the imported
modules but they are only active if the modules are opened in the editor at the time of
debugging.
- The modules can only be opened in the editor during the debugging session by stepping in
repeatedly until reaching the module.
- There should not be any breakpoints set in modules from the same server which are not
involved in the current debugging session.
- No support for profiling when an
XQuery transformation is executed in the debugger.