Thanks David, for this quick heads-up. We can work around it right now, and it's good to know that it will be available in a next release.
Out of curiosity, is there a way to work around it, from a database perspective (using fields or what have you), as opposed to massaging the data in a way as to avoid this scenario? cheers, Jakob. On Tue, May 22, 2012 at 3:00 PM, David Sewell <[email protected]> wrote: >> when I create an element range index for an element, then this index >> will index *all* occurrences of this element whatever their position >> in the document. Is there a way to restrict the element to some given >> context (maybe expressed as an xpath), such as only if this element >> has that parent or that attribute? > > This is a feature that will be implemented in the next release of MarkLogic > (5.1); it was demoed at the annual conference in DC a couple of weeks ago. But > it's not possible in earlier releases. > > > -- > David Sewell, Editorial and Technical Manager > ROTUNDA, The University of Virginia Press > PO Box 400314, Charlottesville, VA 22904-4314 USA > Email: [email protected] Tel: +1 434 924 9973 > Web: http://rotunda.upress.virginia.edu/ > _______________________________________________ > General mailing list > [email protected] > http://community.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list [email protected] http://community.marklogic.com/mailman/listinfo/general
