…definitely a (fairly new) bug, and one that should be fixed soon [1]. I have opened an issue to track this down.

Thanks, Christian

[1] https://github.com/BaseXdb/basex/issues/2054

On Tue, Dec 7, 2021 at 10:31 AM Martin Honnen martin.honnen@gmx.de wrote:

Am 07.12.2021 um 10:16 schrieb Marco Lettere:

...

Hi all,

Just because "abc" || () returns "abc", it felt natural to me that <x attr="abc{()}"/> should return <x attr="abc"/> but I get <x attr=""/> instead.

This is on a 9.6.1.

I can't recall whether this has always been like that thus it's one of my xquery shortcomings or if actually something strange is going on here ...

I would see that as a BaseX bug.

I'll wait for the Winter Edition since I easily could re-arrange for the specific point.

But your usual effort is well appreciated!

Thanks Chrisitan.

M.

On 07/12/21 11:40, Christian Grün wrote:

…fixed and deployed [1]. BaseX 9.6.4 will be released in December.

[1] https://files.basex.org/releases/latest/

On Tue, Dec 7, 2021 at 11:04 AM Christian Grün christian.gruen@gmail.com wrote:

...

…definitely a (fairly new) bug, and one that should be fixed soon [1]. I have opened an issue to track this down.

Thanks, Christian

[1] https://github.com/BaseXdb/basex/issues/2054

On Tue, Dec 7, 2021 at 10:31 AM Martin Honnen martin.honnen@gmx.de wrote:

...

Am 07.12.2021 um 10:16 schrieb Marco Lettere:

...

Hi all,

Just because "abc" || () returns "abc", it felt natural to me that <x attr="abc{()}"/> should return <x attr="abc"/> but I get <x attr=""/> instead.

This is on a 9.6.1.

I can't recall whether this has always been like that thus it's one of my xquery shortcomings or if actually something strange is going on here ...

I would see that as a BaseX bug.