Hi Christian,
On Mon, 8 Apr 2019 at 15:40, Christian Grün
wrote:
> Hi Reece,
>
> First of all, thanks for your marvellous and always up-to-date
> XQuery/BaseX plugin for IntelliJ. We have included it in our Wiki just
> recently [1].
>
Thanks :).
> > I could display the timings, like in the Ba
Dear Michael,
the main reason why the PARALLEL option exists in BaseX is that a
single query should never block other queries that run in parallel.
It’s perfectly fine to have BaseX applied in environments with
hundreds of parallel requests. As Marco indicated, parallel access
leads to random acce
Hi Martin,
I have relaxed the type checking of map arguments. Inter alia,
booleans will be treated similarly to the string values 'yes' and
'no', and functions calls like the following one will now be evaluated
as expected:
serialize(1, map { 'indent': true() })
A new snapshot is online. Adapt
Hi Michael,
there has been a lot of discussion related to this issue. The most
significant result that has alway clearly emerged and that Christian is
always evangelizing us about is that beeing DB -access strictly serial,
querying in paralllel is causing only trouble unless the data is
actual
Hi Reece,
First of all, thanks for your marvellous and always up-to-date
XQuery/BaseX plugin for IntelliJ. We have included it in our Wiki just
recently [1].
> I could display the timings, like in the BaseX GUI. Is there a way to get
> this information using the org.basex.api.client interfaces?
Hallo,
ich versuche gerade, BaseX hier für eine zentrale XML-DB zu evaluieren.
Die DB ist read-only. Wir haben also keinerlei Updates.
Wir haben verschiedene XQuery-Queries(?), die abgesetzt werden, dabei
ist aufgefallen, dass wenn ich mehrere Queries parallel starte die
Antwortzeiten unverhä
6 matches
Mail list logo