Hi Christian, hello all,
to write a new index to get better results out of mostly mixed-content
elements, I have to delete some elements:
db:create('index', for $item in db:open('data') return $item update delete node
.//(note|sic), db:open('data')/db:path(.))
After that I have to remove some
Hello all,
Processing hundreds of thousands of zips, using db:add to to append small XML
fragments from each into a single DB, I notice that the process becomes
successively slower. Without having done any proper profiling, and aware that I
might be looking in the wrong direction here, would
> Improper use? Potential bug? Your feedback is welcome:
> Contact: basex-talk@mailman.uni-konstanz.de
> Version: BaseX 8.3.1
> Java: Oracle Corporation, 1.8.0_45
> OS: Mac OS X, x86_64
> Stack Trace:
> java.lang.ArrayIndexOutOfBoundsException
Hm… Could you provide us with the full stack trace?
> to get
> This is only an illustrative example, not a real text.
> from
> This is only an illustrative example, not a real text.
>
> Is there any way, to do it with the help of BaseX XQuery Update?
There are hundred ways ;) One looks as follows:
db:create(
'index',
for $item in
Hello again,
I got the following error:
Error:
Improper use? Potential bug? Your feedback is welcome:
Contact: basex-talk@mailman.uni-konstanz.de
Version: BaseX 8.3.1
Java: Oracle Corporation, 1.8.0_45
OS: Mac OS X, x86_64
Stack Trace:
java.lang.ArrayIndexOutOfBoundsException
after running:
Hi Hondros,
> Processing hundreds of thousands of zips, using db:add to to append small
> XML fragments from each into a single DB, I notice that the process becomes
> successively slower. Without having done any proper profiling, and aware
> that I might be looking in the wrong direction here,
Hi Christophe,
It's possible to query Basex directly from XSLT. However this can be
cumbersome because you need a lot of escapes to correctly execute the
query. If you only need to query a relative small XML you can avoid
this by getting by getting the complete XML and use a normal xpath in
the
Hello,
I have a small database of library catalog records that I am trying to run
some simple queries on, but I'm running into a namespace problem.
Some docs in the database have the following structure, with a wrapper
collection element and two record elements:
http://www.loc.gov/MARC21/slim;
Hi,
I have sample dtd file such as below, I want to add the dtd file as is in baseX.
Since the dtd file is not in xml format, there are currently two option I can
thought about
1. Use TEXT as input format
When I add it using baseX client UI, I got following output. Since we just need
In principle it looks like openshift-basex-quick-start might be able to
work round the problem by changing the .openshift/stop script to use other
means to stop the server e.g."kill".
/Andy
On 7 January 2016 at 01:59, C. M. Sperberg-McQueen wrote:
>
> On Jan 6, 2016,
Sorry, never mind. I see that the documents that lack are namespace
declarations are just not well formed. Actually, I'm a little surprised
that it was possible to save them to the DB in the first place!
Thanks,
Tim
--
Tim A. Thompson
Metadata Librarian (Spanish/Portuguese Specialty)
Princeton
Using a Java client, we are seeing operations take much longer (e.g.
2x+) when BaseX is remote vs when local (on the same machine). All
machines are virtual Windows. Any ideas why?
I'm running into a problem that perhaps others here can help with.
It appears to be almost identical to the problem reported by "P.C."
on 5 March 2014 under the subject line 'BaseX server.close() "Connection
refused" in Openshift' [1]; the mail record in the basex-talk archive
doesn't show a
Thanks Christian, but I've satisfied myself that the slowdown is due to the
size of the DB being added to by timing a sample set against an empty database.
No big deal, and I can easily work around it.
Cheers,
Constantine
-Original Message-
From: Christian Grün
14 matches
Mail list logo