Seiferle
Cc: BaseX
Betreff: Re: [basex-talk] following-sibling axis -- real data example
Gentlemen (especially Michael)!
My follow-up to my original question from a few days ago:
XML:
A
toto. -A
substantia
.
XPATH:
//clause[word and not(word[not(@lexmorph) or @lexmorph
On Fri, 2019-03-01 at 13:50 -0800, Mark Bordelon wrote:
> I have tried using the -w option’s true and false values, but my
> results are always as above.
>
> Any ideas?
Try removing all whitespace between tags that's not part of the actual
document and see if you get different results; if so, i'd
Gentlemen (especially Michael)!
My follow-up to my original question from a few days ago:
XML:
A
toto. -A
substantia
.
XPATH:
//clause[word and not(word[not(@lexmorph) or @lexmorph='' or
contains(@lexmorph,' ')])]/string-join(word[not(@implicit)]/concat(
Hi Mark,
as Martin already stated, the '-w‘-Option has to be active at import time,
otherwise the whitespace will be chopped.
If I were to do it, I’d reindex all data and explicitly mark all elements that
should preserve whitespace, if this is not an option I’d reindex all data with
whitespa
Am 26.02.2019 um 18:52 schrieb Mark Bordelon:
A follow-up: starting basex -w does NOT seem to solve completely my
issue after all. Real data (more complicated than the simplified
example) still does not query correctly: text nodes from after later
elements are displayed in the place of null te
A follow-up: starting basex -w does NOT seem to solve completely my issue
after all. Real data (more complicated than the simplified example) still does
not query correctly: text nodes from after later elements are displayed in the
place of null text nodes.
I’ll try to get a better example, sti
My follow-up was too hasty, and I forgot to mention that I had tried starting
up basex with -w, but it break so many other things that I cannot use this
GLOBAL approach.
I need to instruct either at the XQUERY command level or at the xml file level.
By the way, Kirstian, THANK YOU does work in th
Thanks Martin and Michael for the “sofortige Antoworten”.
Forgive my lack of understanding about the particular of whitespace processing
and how BASEX deals with them.
To answer Martin’s questions:
1) I stored that xml (as I do all of my email) in the database using this
commands in the basex she
Hi Mark,
Hi Martin,
yes Martin is right, the whitespace will be chopped by default leading to the
observed behavior.
If you wanted to preserve whitespace globally, you can do that when creating
your database.
If you only want to preserve whitespace for a given element you may do this as
well
Am 26.02.2019 um 07:54 schrieb Mark Bordelon:
But I have a question about some behavior I am seeing in the
*following-sibling* axis that does not seem logical to me.
Here is the data stored in basex:
> xquery /text[@id='test']
Aa
B
Cc
Here is the query on that data:
> *xquery /text[@id
Am 26.02.2019 um 07:54 schrieb Mark Bordelon:
Guten Tag,
Love my basex, have been using it for years. I particularly love being
able to have access to all the powerful 2.0 syntax.
But I have a question about some behavior I am seeing in the
*following-sibling* axis that does not seem logical to
Guten Tag,
Love my basex, have been using it for years. I particularly love being able to
have access to all the powerful 2.0 syntax.
But I have a question about some behavior I am seeing in the following-sibling
axis that does not seem logical to me.
Here is the data stored in basex:
> xquery /
12 matches
Mail list logo
