Then to pass the XQuery test suite you probably use CHOP=OFF.
Are there other settings needed to be compliant?
On woensdag 17 februari 2021 00:04:38 CET Christian Grün wrote:
> Yes, you are certainly right. I think it was around 2007 when we chopped
> whitespaces by default, although we knew it
Yes, you are certainly right. I think it was around 2007 when we chopped
whitespaces by default, although we knew it didn't comply with the
specification. One reason was that we rarely worked with mixed-content data
at that time, and the whitespace indentations increased the size of
databases and
Thanks for the context.
Still, it does not explain the difference in behavior bestween doc() and
parse-xml().
As far as I understand the XDM specification, whitespace may be ignored by the
parser if there is a DTD or XML Schema that says that an element is not PCDATA
(DTD) or mixed (XML
There is an old (and still open) issue on GitHub [1] that might give you
some more insight into the history of whitespace chopping in BaseX.
Hope this helps
Christian
[1] https://github.com/BaseXdb/basex/issues/913
Jos van den Oever schrieb am Di., 16. Feb. 2021,
22:41:
> Hi Christian,
>
>
Hi Christian,
Yes, writing 'CHOP=OFF' in .basex stops the vanishing of whitespace.
But where in the XQuery or XDM spec does it say that whitespace handling when
parsing is implementation dependent?
Cheers,
Jos
On dinsdag 16 februari 2021 22:10:30 CET Christian Grün wrote:
> Hi Jos,
>
>
Hi Jos,
Whitespaces will be preserved if the CHOP option is disabled. You can make
this a default by adding CHOP=false in your .basex configuration file [1,2].
Hope this helps,
Christian
[1] https://docs.basex.org/wiki/Full-Text#Mixed_Content
[2] https://docs.basex.org/wiki/Configuration
Dear all,
First off: BaseX is great to work with. I use it for a few statically
generated websites.
But I recently found what might be a bug.
Some whitespace vanishes when loading xml files. E.g. this xml file:
```test.xml
a b c d e
```
run like this:
doc('test.xml')
gives:
a bcd e
Hi Christian,
Thanks for your answer.
Both files are in the same local directory when loading into BaseX.
I've tried several things like removing the xpointer (to make sure it's not the
problem) and the fallback scenario.
When I add the file into BaseX I now have the following message when
There may be various solutions ;) A minimized code example that
demonstrates your procedure could be helpful here.
On Tue, Feb 16, 2021 at 3:21 PM Tim Thompson wrote:
>
> Yes, the insert operations also involve lookups against a couple of full-text
> indexes (using ft:search()). The entries in
Hi Pascal,
Welcome to the list, thanks for your contribution.
> Basically i have a main file which contains this xinclude instruction :
>
> Pièce
> non encodée pour le moment.
>
> In my baseX database i have my main file and the EP15.xml file which contains
> this instruction :
The XINCLUDE
Hi Tim,
> Is it possible to put updating expressions in a library module function (with
> the name of the database hard coded) and then call from the function within
> jobs:eval() in a main module?
Yes, it should be. Here’s a little example (create database 'x' first):
lib.xqm:
module
11 matches
Mail list logo
