We have a BaseX application that uses the BaseX REST API. A number of GET
requests are failing with an HTTP 400 Bad Request response. Looking at the
BaseX logs, I find that BaseX is internally throwing
java.lang.ArrayIndexOutOfBoundsException for these HTTP 400 Bad Request
failures:
[GET]
On Fri, 2020-06-05 at 12:38 +, ETANCHAUD Fabrice wrote:
> Hi all BaseX users,
>
> When I search for 'YET_ANOTHER_SILLY_KEYWORD', ft:search gives me all
> text nodes containing any of the YET ANOTHER SILLY KEYWORD words.
Does it work to put the phrase in double quotes?
Fabrice - my apologies. I see now that my suggestion was very naive. I hope
I didn't waste your time.
Sorry for the noise.
Best,
Bridger
On Fri, Jun 5, 2020 at 10:23 AM Bridger Dyson-Smith
wrote:
> Hi Fabrice -
>
> Maybe something like
> ft:search("the-database", "YET_ANOTHER_SILLY_KEYWORD",
Hi Fabrice -
Maybe something like
ft:search("the-database", "YET_ANOTHER_SILLY_KEYWORD", map { "mode":
"phrase", "ordered": true() })?
I confess that I don't know the full text module behavior at all, but I
coincidentally had it open... Anyway, I hope that's helpful.
Best,
Bridger
On Fri, Jun
Hi all BaseX users,
When I search for 'YET_ANOTHER_SILLY_KEYWORD', ft:search gives me all text
nodes containing any of the YET ANOTHER SILLY KEYWORD words.
I tried the different search modes, but could not find a way to get ft:search
return only the text nodes containing the concatenation.
Does
Hi Buddy,
If you call Java code from XQuery, your nodes might be copied to a
Java-specific representation, and the node identity might change. If
you stick to the native data structures (did you try the XQuery map),
everything should be fine.
Hope this helps,
Christian
On Fri, Jun 5, 2020 at
6 matches
Mail list logo
