Thanks Johan and Matti for useful suggestions.
Cutting down on the chunks seems to be a viable alternative.
It would have been nice, though, to have a robust harvester in XQuery that
could take on anything, although the recursive version works fine as long
as the dataset consist of a couple of
Hello Lars,
just a thought (and really just a pointer, I am neither a purely
functional guy and also I feel like I am missing something obious...):
Maybe you could rewrite the recursive approach using higher order
functions. Consider a query like the following
hof:scan-left(1 to 100,
map { "tok
Thanks for pointer!
Code is rewritten using hof:until() and tested towards a particular set at
our national provider of library data.
The script still accumulates data, so it will probably still run into
memory troubles with larger datasets, but the stack-overflow should be
taken care of.
For an
It seems that maven central is not up to date with the latest basex
version. I see here that there's only version 7.3.1 whereas on the basex
website the latest version is 8.4.4
http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.basex%22
Are there any plans to keep maven central up to date with
Hi,
I seemed that this is the behavior if disabling REST Service in web.xml
(BaseX.war deploymented on Tomcat), but this does not happen. The
surprise is that the functions are accessible from anywhere, if access
is not protected by other methods.
I'm doing wrong, what should be setting? I u
I'm not sure I understand how to do that. If the call to baseX.jar start
has everything embedded together, how would I split it up to control each
part?
I'm a programmer, not a sysadmin, so it might be a basic question, but I'm
not finding anything in the doc.
6 matches
Mail list logo