On 01/30/2015 05:18 PM, Christian Grün wrote:
/gmd:MD_Metadata/gmd:identificationInfo/sdn:SDN_DataIdentification/gmd:descriptiveKeywords[1]/gmd:MD_Keywords/gmd:keyword[2]/sdn:SDN_ParameterDiscoveryCode/@codeListValue
How can I remove *?
Simply remove the predicate; a[*]/b is the same as a/b.
Maybe I wasn't clear. The actual number appears in the xml file, e.g.,
gmd:descriptiveKeywords[1]
Anyway, I've removed all [*] and I get the same correct result, however
the processing time is doubled...
* In some cases, if you know that an element name is distinct, you can
get rid of all the explicit child steps and directly address the node
via the descendant axis.
Thanks, but it's not relevant in my case.
Is it because the element names are not distinct? Or is it because
your input form allows users to choose arbitrary paths for arbitrary
documents?
The element names are not distinct.
Sure, I'l also try BaseX 8.0 and compare. Should I recreate the db importing
the xml files for testing the improved indexing?
We have actually improved support for collections, but the database
format itself has not changed, so it shouldn't make a difference in
your case.
Christian
[1] http://files.basex.org/releases/latest
On Fri, Jan 30, 2015 at 3:55 PM, Menashè Eliezer
<melie...@ogs.trieste.it> wrote:
Hello,
I wonder if the attached query can be optimised. I'm attaching all
relevant
information.
Basex 7.9, Debian, powerful server.
This is just an example. The queries will be built based on a compilation
of
a search form.
Any help would be appreciated.
40 seconds are not acceptable.
--
With kind regards,
Menashè
--
With kind regards,
Menashè
With kind regards,
Menashè
