I have added an issue on the effects of (XML) parsing options; you are
invited to leave comments:
https://github.com/BaseXdb/basex/issues/905
__
On Thu, Mar 20, 2014 at 11:15 PM, Christian Grün
wrote:
>> HURRA! -wi fixes the problem! Thank you very much, Christi
Hi Stefan,
our team member was so kind to fix this issue just in time [1]. A new
snapshot is online [2].
You may be interested to hear that we will soon add a BaseX TEST
command, which is supposed to replace the XQuery functions. This
command will also support updating unit functions.
Best,
Chri
Hi Fabrice,
thanks for your feature requests. Luckily, all of these are listed in
our GitHub issue tracker. I can't give you any timeline yet.
> How does BaseX team provide non-open-source features ?
BaseX itself will stay open source, no doubt about that. All of our
commercial offerings are bui
Thanks, this was helpful. It's on our list:
https://github.com/BaseXdb/basex/issues/903
On Fri, Mar 21, 2014 at 12:13 PM, Stefan Sechelmann
wrote:
> Hi Christian,
> thank you for looking into this. The test is run from an ant target that uses
> exec to run a standalone basex instance:
>
>
Hi Christian,
thank you for looking into this. The test is run from an ant target that uses
exec to run a standalone basex instance:
${xqunit_bibtex_out}
Thanks for trying. How do you run your test?
On Fri, Mar 21, 2014 at 11:55 AM, Stefan Sechelmann
wrote:
> I truied, it does not work:
> [copy] Copying 21 files to
> /Users/sechel/workspace/dgdgallery/build/backend/data
> DGD Bibtex test suite:
> [exec] Improper use? Potential bug? Yo
I truied, it does not work:
[copy] Copying 21 files to
/Users/sechel/workspace/dgdgallery/build/backend/data
DGD Bibtex test suite:
[exec] Improper use? Potential bug? Your feedback is welcome:
[exec] Contact: basex-talk@mailman.uni-konstanz.de
[exec] Version: BaseX 8.0 beta e3
> collection('db')/a[@att = 'xxx' and b/text() = 'zzz']
> on my laptop (Intel I7, 8 GB Ram and SSD) takes some 5 to 7 seconds.
How does your query plan look like?
> What I noticed and this is feeling strange is that the time is often spent
> in rather similar proportion between query compilation
Hi Marco,
> I've a few questions related to namespaces. I've noticed that on one of the
> info panels of the the GUI all the namespaces of the documents stored in a
> DB are listed. Is there a way to get this information from inside an XQuery?
Something like this may help:
let $names := db:ope
Hi Marco,
you could generate this list using the functions
fn:in-scope-prefixes#1 and fn:namespace-uri-for-prefix#2
As far as I know there is no such function. But maybe I am wrong – as there is
plenty of undiscovered features in BaseX :)
hope this helps
Arve
On 21 Mar 2014, at 09:58, Marco
Hello to everyone,
while trying to trace the performance I could expect from my RestXQ app
I created a DB with something like 300/400k documents. For the test the
documents are rather homogenoeus and stored plainly in the DB root
collection.
I had two major objectives.
1) understand the beha
Hello all,
I've a few questions related to namespaces. I've noticed that on one of
the info panels of the the GUI all the namespaces of the documents
stored in a DB are listed. Is there a way to get this information from
inside an XQuery?
My problem is that I have to perform queries that are dy
12 matches
Mail list logo
