(2) cts:uri-match() doesn't make the utility of Query Console Explore any better.
I haven't applied this collection strategy idea I just had to my data yet, but I hope that the collection links displayed in the Explore table will provide navigation to the filtered list of documents in that collection. Otherwise using collections won't work either. The biggest advantage I see to XQuery is that as a declarative language it just works. It reduces the problem to a simple declaration of what I want in a result. I don't need to think imperatively. The details of how to produce a result are left up to the platform. The complexity of the system is reduced significantly. The tools which surround the XQuery need to be just as simple. I haven't read all the FAQ's and tutorials that exist for MarkLogic so many of my questions will likely be RTFM. I jumped in with preconceived notions (learned from oXygen and eXistDB and xDB and XMLSpy and such) about what I need in a development environment to optimize my ability to experiment with XQuery analysis of large data sets. A would hope the Explore view would let me explore a three dimensional hierarchy, not just page through a two dimensional table of 3500 pages. That being said, eXistDB doesn't have a way to cancel a query in their explorer so I very much appreciate MarkLogic providing for that option.
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
