Re: [xml-dev] What is the general direction you are seeing thesedays to

["HILLMAN, Tomos" <tomos.hillman@oup.com>]

I’ve not used it, but people in my team have found Sedna to be very quick (if not as fully featured as eXist and ML): http://www.sedna.org

T

From: Ihe Onwuka <ihe.onwuka@gmail.com>
Reply-To: "ihe.onwuka@gmail.com" <ihe.onwuka@gmail.com>
Date: Thursday, 5 March 2015 14:03
To: "Costello, Roger L." <costello@mitre.org>
Cc: "xml-dev@lists.xml.org" <xml-dev@lists.xml.org>
Subject: Re: [xml-dev] What is the general direction you are seeing these days to store and query lots of large complex XML?

I just discovered  (by way of an abort) that there  is  a 64k limit on the number of distinct element and attribute names you can have in an eXist database and so am moving over to trial MarkLogic.

Generally I have found that compacting the size and number of nodes in your XML can mitigate the onset of the dreaded heap space error but such techniques can only take you so far especially when  querying across collections.

On Thu, Mar 5, 2015 at 8:02 AM, Costello, Roger L. <costello@mitre.org> wrote:

Hi Folks,

I have large, complex XML that I want to be able to query using XPath and XQuery.

What is the general direction you are seeing these days to store and query lots of large complex XML?

/Roger

_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

Oxford University Press (UK) Disclaimer

This message is confidential. You should not copy it or disclose its contents to anyone. You may use and apply the information for the intended purpose only. OUP does not accept legal responsibility for the contents of this message. Any views or opinions presented are those of the author only and not of OUP. If this email has come to you in error, please delete it, along with any attachments. Please note that OUP may intercept incoming and outgoing email communications.