MarkLogic World 2020 Live Keynote – Register Now

All Posts By

Evan Lenz

The simple mapping operator (!), a feature of XQuery 3.0, promises to transform the face of XQuery programming style. Check it out.
XQuery has these 12 comparison operators: eq, ne, lt, gt, le, ge, =, !=, , =. Isn't that about 6 too many?
Namespace-related bugs are a pain in the neck. You can avoid a large class of them by pretending that the name() function never existed (and avoid using it).
Do you use the text() node test a lot? You may need to get help. Fortunately, you need look no further than this article.
How do you control how your query or stylesheet results will be serialized (encoding, indentation, etc.)? There are several options for controlling output options.
What is meant by the term "fragment" in MarkLogic? How is it different from a "document"? Are there different kinds of fragments?
Namespace wildcards are handy shortcuts -- sometimes. But more often than not they should be avoided. Read more to learn why.
Learn how MarkLogic's Search API made it easy to implement faceted search for an example website.
Should you use the "fn:" prefix when calling the built-in XQuery functions? This post discusses the pros and cons.
The xdmp:query-trace() function is a useful tool in helping to understand how MarkLogic evaluates queries. Why does a query run fast or slow?
This website uses cookies.

By continuing to use this website you are giving consent to cookies being used in accordance with the MarkLogic Privacy Statement.