MARKLOGIC SERVER

MORE WITH FIELDS
Fields also provide a way to create singular indexed values out of complex XML.
Imagine that you have XML structured like this:
John
Fitzgerald
Kennedy
You can create a field named "fullname" against defined to contain all of its
child elements. Its singular value will be the person's full name as a string. You can
create another field named "simplename" against but excluding . Its
singular value will be just the first and last names as a string. Using cts:field-valuequery()
you can do optimized queries against either of these computed values. It's
much faster than computing values as part of the query. Within the Universal Index,
each field simply adds term lists, one for each value.
As mentioned previously, you can even create a range index against a field. Then you
can sort by, constrain by, and extract values not even directly present in the documents.
REGISTERED QUERIES
Registered queries are another performance optimization. They allow you to register
a cts:query as something you plan to use repeatedly and whose results you'd like
MarkLogic to remember for later use.
Let's say that you're going to generate a report on the number of Firefox browsers per
day that hit any index.html page on your site. You may want to register the portion of the
query that doesn't include the day, then use it repeatedly by intersecting it with the
day constraint.
For the code below, let's assume that we have a set of documents in the fact
namespace that records data about visiting browsers: their name, version, and
various attributes, and the session ID in which they appear. You can think of those
documents as the XML equivalent of a fact table. Let's assume that we also have a set
of documents in the dim namespace (the XML equivalent of a dimension table) that
records data about particular page hits: the page they hit, the date on which they were
seen, and other aspects of the request, such as its recorded performance characteristics.
77