Hi Thufir,
> That's really the end goal: just running XQuery against html.
In that case, you can simply use "new XQuery(...).execute(ctx)". Any
query that works in the GUI can be supplied as argument.
> The only query I can get working against the html is for the query
> string to be "text()" o
Hi Andreas,
If you send multiple commands via a single REST operation, they will
be treated as a single transaction. In order to preserve the ACID
principles, no other operations will run in parallel. If you want to
run concurrent operations, you should be fine if you send your
commands one by one
The WebDAV implementation is definitely not the one that provides best
performance in BaseX. Nevertheless, I think I’ll have a look at the
use case you describe. Some questions in return:
> I re-verified the behavior on a third (fast) machine with SDD and the result
> as still bad with an average
Dear Adam,
I remember that Andy Bunce has given an answer on this in a previous
post [1]. I haven’t tried this by myself (in most scenarios I got my
hands on, additional proxies are used to handle https). Feel free to
report back to us if this works for you; we might include your
observations in o
Are you saying that a write transaction blocks pending READ requests until the
transaction
has been committed?
On 7 Jan 2019, at 11:14, Christian Grün wrote:
> Hi Andreas,
>
> If you send multiple commands via a single REST operation, they will
> be treated as a single transaction. In order to
On 7 Jan 2019, at 11:20, Christian Grün wrote:
> The WebDAV implementation is definitely not the one that provides best
> performance in BaseX. Nevertheless, I think I’ll have a look at the
> use case you describe. Some questions in return:
>
>> I re-verified the behavior on a third (fast) machin
6 matches
Mail list logo
