Hi Menashè,
> Should I expect to see the usage of an index for each of the where phrases?
Usually, only one predicate will be rewritten for index access, and
the remaining conditions will be answered sequentially.
> Have a nice weekend!
Enjoy,
Christian
> Menashè
>
> On Fri, 30 Jan 2015 18:11
Hi Christian,
Interesting! I'll check it when I'm back at the office and keep you
updated.
I'll use for $x in
collection("ALL-CDIS")/gmd:MD_Metadata/gmd:identificationInfo/sdn:SDN_DataIdentification
as you've suggested.
Should I expect to see the usage of an index for each of the where phrases?
H
Hi Menashè,
Thanks for the XML samples you sent me in private. I noticed that the
index rewritings will only be triggered if you formulate your query as
follows:
OLD:
for $x in collection("ALL-CDIS")
where $x/gmd:MD_Metadata/gmd:identificationInfo/...
return ...
NEW:
for $x in collection
Could you possibly provide me with a small snapshot of your data
sources (one, two documents might be sufficient)?
On Fri, Jan 30, 2015 at 5:52 PM, Menashè Eliezer
wrote:
> Almost the same speed with version 8.0.
> No indexing (no "applying" in the query info).
> As I've attached before, indexes
Almost the same speed with version 8.0.
No indexing (no "applying" in the query info).
As I've attached before, indexes are active for this DB.
With kind regards,
Menashè
On 01/30/2015 05:31 PM, Christian Grün wrote:
It's indeed interesting that your query does not use any of the
existing index
It's indeed interesting that your query does not use any of the
existing index structures (if they did, you would find strings like
"applying text index" or "applying attribute index" in the query
info). Maybe/hopefully things look different with Version 8.0.
On Fri, Jan 30, 2015 at 5:26 PM, Mena
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.
Ma
/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.
>> * In some cases, if you know that an element
Hi Christian,
Thank you for your reply. Updated files are attached.
On 01/30/2015 04:35 PM, Christian Grün wrote:
Hi Menashè,
First of all, I wonder if your query really does what you want it to
do. I noticed for example that some of the where conditions start with
"$x/", while others start
Hi Menashè,
First of all, I wonder if your query really does what you want it to
do. I noticed for example that some of the where conditions start with
"$x/", while others start with "/" and some others start with no
slash. Is this intentional?
Some more comments:
* I would recommend you to avoi
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.
So reordering the conditions for having smaller subset right from the
> Sorry I missed it. I am expecting the ordered output in the XML File using
> file:append().
How would that look like?
> Also I am still using the 7.6 version.
What happens with 7.9 or the latest snapshot?
>
> On Fri, Jan 30, 2015 at 1:30 PM, Christian Grün
> wrote:
>>
>> Hi John,
>>
>> > bu
Hi Christian,
Sorry I missed it. I am expecting the ordered output in the XML File using
file:append().
Also I am still using the 7.6 version.
On Fri, Jan 30, 2015 at 1:30 PM, Christian Grün
wrote:
> Hi John,
>
> > but when I open the newly created file I didn't get the expected (sorted)
> > ou
Hi John,
> but when I open the newly created file I didn't get the expected (sorted)
> output !!
Pity. Could you please indicate what output you would expect?
I am getting (and expecting) this result:
AAbAnDP
Best,
Christian
14 matches
Mail list logo