Hi,
I have a problem with whitespace handling of the default BaseX XML parser. If I have:
<s>and <a>this</a> is</s>
the parser deletes the spaces after "and" and before "is". Why not preserving the space as default option here? This kind of space is very important.
I know that with adding xml:space I can solve the problem, but this is not easy to do automatically (moreover I cannot do this with copy/modify because all spaces are deleted after adding xm:space ).
Is there a parameter which forces the parser to keep the spaces, without modifying the file? And in general, can the behavior of the parser be changed?
Hi,
On 29.01.2017 at 23:09, meumapple wrote (with possible deletions):
Is there a parameter which forces the parser to keep the spaces, without modifying the file? And in general, can the behavior of the parser be changed?
have you looked at the `CHOP` option [1]?
Hope that helps, Leo
Perfect. It works. Thanks.
Il giorno 29 gen 2017, alle ore 23:28, Leonard Wörteler leonard.woerteler@uni-konstanz.de ha scritto:
Hi,
On 29.01.2017 at 23:09, meumapple wrote (with possible deletions):
Is there a parameter which forces the parser to keep the spaces, without modifying the file? And in general, can the behavior of the parser be changed?
have you looked at the `CHOP` option [1]?
Hope that helps, Leo
Hi all,
I have BaseX version 8.3 running on Ubuntu and Tomcat. Up till recently eveything was running nice and reliable. Lately however I see some queries, that otherwise may take a few seconds to complete, to run abnormally long. So long that they will eventually cause Tomcat, and thus BaseX, to stop running. In the BaseX log I can locate these queries. One had an execution time of a whopping 156096,382 seconds ... (!)
My questions: 1. What can cause BaseX to take so long to run a query that otherwise takes just a few seconds? 2. Is there a way (configuration option) to set a timeout for queries run as admin? From the documentation I conclude that admin operations are never timed out. But the query that ran so long is just a read query. No updates or insertions are performed. So why was it not timed out?
Thanks in advance.
Paul
basex-talk@mailman.uni-konstanz.de
-
Leonard Wörteler -
meumapple -
Paul Swennenhuis