Re: [basex-talk] ft search with wildcards does not work with higher Unicode characters

I just tried to use the gh1800 test to replicate my problem and it does not show there. It fails using the GUI. Am 06.02.2020 um 13:35 schrieb Christian Grün: Hi Omar, Yes, that seems to solve the problem partly. Using wildcards now yields the same result as no wildcards. Glad to hear.

Re: [basex-talk] ft search with wildcards does not work with higher Unicode characters

Hi, Yes, that seems to solve the problem partly. Using wildcards now yields the same result as no wildcards. But if there is a complex unicode character in the search string, "." for one character looses its meaning. collection('testdata')//*[text() contains text 'r.{1,1}ḥ' using

Re: [basex-talk] ft search with wildcards does not work with higher Unicode characters

The following XQuery run in the GUI (pulled from github and built a few minutes ago from source) ft:tokens('testdata'), ft:search('testdata', 'r.ḥ', map {'wildcards': true()})/.., '--' ,collection('testdata')//*[text() contains text 'r.ḥ' using wildcards] yields rwḥ -- with

Re: [basex-talk] ft search with wildcards does not work with higher Unicode characters

> I can try. But what you tell me and what I saw with the unit test function I > guess the GUI does something that can't be observed when using scripts. Maybe some options are still active in your GUI that are not reflected in the script? Does the script work if you run it on command line? >

Re: [basex-talk] ft search with wildcards does not work with higher Unicode characters

Hi Omar, > Yes, that seems to solve the problem partly. Using wildcards now yields the > same result as no wildcards. Glad to hear. > But if there is a complex unicode character in the search string, "." for one > character looses its meaning. > … > Would you like a PR for the test gh1800

Re: [basex-talk] ft search with wildcards does not work with higher Unicode characters

> I just tried to use the gh1800 test to replicate my problem and it does > not show there. It fails using the GUI. I need your help: What does not show there? What fails, what happens? > Am 06.02.2020 um 13:35 schrieb Christian Grün: > > Hi Omar, > > > >> Yes, that seems to solve the problem

Re: [basex-talk] ft search with wildcards does not work with higher Unicode characters

Looks we are getting closer. I have attached a little command script; do you think you can adapt it such that it captures the potential bug? On Thu, Feb 6, 2020 at 1:51 PM Omar Siam wrote: > > The following XQuery run in the GUI (pulled from github and built a few > minutes ago from source) >

Re: [basex-talk] ft search with wildcards does not work with higher Unicode characters

Hi, I can try. But what you tell me and what I saw with the unit test function I guess the GUI does something that can't be observed when using scripts. Unfortunately I get new problems with 9.3.2 Beta: declare function local:maptest() as map(xs:string, xs:string) { let $xml := <_

Re: [basex-talk] ft search with wildcards does not work with higher Unicode characters

I think I've got it: for reasons I am not 100% sure about right now a usually select diacritics: true() So the following does not work as expected: db:open('testdata')//*[text() contains text 'r.{1,1}ḥ' using wildcards using diacritics sensitive]

Re: [basex-talk] ft search with wildcards does not work with higher Unicode characters

Great! Confirmed and registered [1]. [1] https://github.com/BaseXdb/basex/issues/1802 On Thu, Feb 6, 2020 at 3:03 PM Omar Siam wrote: > > I think I've got it: for reasons I am not 100% sure about right now a usually > select diacritics: true() > > So the following does not work as expected:

[basex-talk] Reg : XQUERY Performence

Dear Basex Team, we have one collection with 3,00,000(3 lakhs) xmls and the collection size is 4 gb,on this collection we are running xquery ,this query taking more than 20 minutes.Here we need to run xquery all 3 lakhs xmls(for report purpose we need to get data from all xmls) . Note : Same