StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Simple answer is "No". But there are of course ways forward.</p> <p>If you're amenable to adding an attribute (but leaving the element name unchanged), you could constrain the field by that, e.g.:</p> <pre><code><Device> <Name _field="DeviceName">device1</Name> ... </Device> </code></pre> <p>The attribute/value pair can be anything you want; you just have to tell the field definition, what it is. A good practice might be to <code>namespace-qualify</code> the attribute, so it's clearly an annotation from a different vocabulary, e.g.:</p> <pre><code><Device xmlns:field="http://example.com/field-annotations"> <Name field:name="DeviceName">device1</Name> ... </Device> </code></pre> <p>Range indexes can currently only be tied to element values, attribute values, and field values. Fields let you abstract a little bit from the underlying structure, but not as much as a more generic mechanism would.</p> <p>Another technique sometimes employed (though I haven't personally tried this) is to use two databases, one that's slightly more "logical" (e.g., a standard format, unchanged) and one that's more <code>database-optimized</code>.</p> <p>Whatever approach you decide, a little more work is necessary.</p> <p>If I were you, I'd probably write an <code>XSLT</code> transform which could be applied on input, and another simple one for returning the original unannotated version if I ever need it.</p> <p>annotate.xsl:</p> <pre><code><xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:field="http://example.com/field-annotations"> <xsl:import href="copy.xsl"/>  <xsl:template mode="add-att" match="Device/Name"> <xsl:attribute name="field:name" select="'DeviceName'"/> </xsl:template> </xsl:stylesheet> </code></pre> <p>cleanup.xsl:</p> <pre><code><xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:field="http://example.com/field-annotations"> <xsl:import href="copy.xsl"/>  <xsl:template match="@field:*"/> </xsl:stylesheet> </code></pre> <p>copy.xsl:</p> <pre><code><xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">  <xsl:template mode="add-att" match="*"/>  <xsl:template match="*"> <xsl:element name="{name()}" namespace="{namespace-uri()}"> <xsl:apply-templates select="@*"/> <xsl:apply-templates mode="add-att" select="."/> <xsl:apply-templates/> </xsl:element> </xsl:template>  <xsl:template match="@* | text() | comment() | processing-instruction()"> <xsl:copy/> </xsl:template> </xsl:stylesheet> </code></pre> <p>You can apply <code>annotate.xsl</code> using <code>xdmp:xslt-invoke()</code> in your application code for inserting documents into the database. Or you can configure <code>annotate.xsl</code> as a transformer in an Information Studio flow.</p> <p>When you want to retrieve the pristine doc, just call:</p> <pre><code>xdmp:xslt-invoke("cleanup.xsl", doc("my-doc.xml")) </code></pre> <p>But for most cases in regular application code, you don't need to clean up the document. Since, the presence of an extra attribute will rarely have any effect there.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload