Dear Johannes,
Thanks for the observation. The third argument was added to the
function just recently, and it was done wrong. I have just fixed this,
a new stable snapshot is available [1]. The next patch release (BaseX
9.1.2) will be released in the near future.
Best,
Christian
[1]
Hello,
I've a question to the response-header() function of the web module.
In my RESTXQ function I try to return a response with HTTP Status 404:
module namespace basex ='basex';
declare %rest:GET %rest:path("/db/{$db}/doc/{$doc}")
%rest:produces("application/xml")
%output:method("xml")
>
> See my first mail…also requests to other arbitrary documents are slow (in
> the range
> of course 700ms and higher).
Well. That’s why I said I’ll have another look at this. Feel free to send
us a link to your data, this might simplify the analysis.
We did not choose
> a vendor specific API
>
> This is not true.
Sounds like a communication problem. My impression is that we are both
right. Did you read our documentation?
On 9 Jan 2019, at 20:48, Christian Grün wrote:
>> Are you saying that a write transaction blocks pending READ requests
> until the transaction
> has been committed?
>
> No. What I was trying to say is that we deliberately designed REST requests
> to be atomic transactions. If you perform
On 9 Jan 2019, at 20:39, Christian Grün wrote:
>>
>> Please check the log entries..there are only HEAD/PROFIND/GET requests
>> on the WebDAV level against a single XML resource.
>>
>
> I just created a collection with 120,000 documents. The time for retrieving
> a single resource was about 100
> Are you saying that a write transaction blocks pending READ requests
until the transaction
has been committed?
No. What I was trying to say is that we deliberately designed REST requests
to be atomic transactions. If you perform multiple updates in a single REST
operation, you can be sure that
>
> Please check the log entries..there are only HEAD/PROFIND/GET requests
> on the WebDAV level against a single XML resource.
>
I just created a collection with 120,000 documents. The time for retrieving
a single resource was about 100 ms; but it took much longer indeed to
request entries of
All die, and O! the embarrassment!
It should indeed!
Thank you, Christian.
On Wed, Jan 9, 2019 at 12:42 PM Christian Grün
wrote:
> Hi Graydon,
>
> $c/descendant::text()[normalize-space]
>
> Maybe it should be as follows?
>
> $c/descendant::text()[normalize-space()]
>
> Cheers,
> Christian
Hi Graydon,
$c/descendant::text()[normalize-space]
Maybe it should be as follows?
$c/descendant::text()[normalize-space()]
Cheers,
Christian
Am Mi., 9. Jan. 2019, 18:35 hat Graydon Saunders
geschrieben:
> Hello!
>
> I'm using BaseX 9.1.1 on Linux.
>
> So I need to go through a whole
Hello!
I'm using BaseX 9.1.1 on Linux.
So I need to go through a whole bunch of documents and emit them in an
obfusticated form so the folks doing publication development can have them
without the client's security people becoming upset. I don't want to
obfusticate the db contents; I just want
11 matches
Mail list logo
