Hi Günter,
> my long-time project (kleist-digital.de) is nearly only based on documents
> (TEI-xml), so I'm working mostly with mixed content.
Thanks for the link to your project. I just remembered the (in)famous
dash in Kleist’s Marquise (»Hier — traf er«), and it was interesting
to look it up
Thanks Christian as always was a quick and detailed response.
1. I am not 100% clear, if you are motivating me towards or against
FULLTEXT indexing :)
2. Yes I am dealing with GBs of XML files. I create new Databases, using
JAVA API using CreateDB class. Should I be using MainOptions to set
Hi Christian,
The behavior I am looking for is getting back false whenever the text following
‘contains text' is reduced to an empty string. Is there a simple what of
checking that?
Thanks,
Ron
On January 3, 2016 at 7:41:47 PM, Christian Grün (christian.gr...@gmail.com)
wrote:
Hi Ron,
>
Hi Mansi,
> 1. Most of my xqueries are of below nature
>
> '/Archives/descendant::apiCalls[contains(@name,"com.sun")]/@name', where
> apiCalls could be 3-4 level under 'Archives'. Xqueries are accessed via REST
The existing index structures won’t allow you to look for arbitrary
sub strings; see
Thanks, Christian. I will look into the solution you suggested. Will need to
cache the stop words to avoid repeatedly opening the file for reading.
Ron
On January 3, 2016 at 8:14:51 PM, Christian Grün (christian.gr...@gmail.com)
wrote:
> The behavior I am looking for is getting back false
Ok. I will do some research and experimenting and report back my experience.
Thanks,
- Mansi
> On Jan 3, 2016, at 7:31 PM, Christian Grün wrote:
>
> Hi Mansi,
>
>> 1. I am not 100% clear, if you are motivating me towards or against FULLTEXT
>> indexing :)
>
> This
By the way, here are two more rewritings to avoid the current sliding
of the let clause:
Variant A:
for $city in doc('factbook')//city/name
let $hits := ft:mark($city[text() contains text 'paris'])
where $hits
let $name := $city/ancestor::country/name
return ($hits, $name)
Variant B:
Hi Ron,
> "Superior Laboratories" contains text { "Medical Affairs" } using stop
> words ( "medical", "affairs” )
I’m pretty sure that "true" is the right answer here. I must admit
that, due to the variety of options provided by the XQFT spec, it’s
often not too obvious what’s going on.
>
Hi Mansi,
> 1. I am not 100% clear, if you are motivating me towards or against FULLTEXT
> indexing :)
This is something you’ll have to answer by yourself; it depends on the
kind of queries and on your ability to store attribute values as
texts.
> 2. Yes I am dealing with GBs of XML files. I
Hi,
I noticed an unexpected behavior with full-text matching using stop words. The
actual code is somewhat complex (it matches CT.gov trials with sponsor studies)
but I was able to distill it to a simple expression:
"Superior Laboratories" contains text { "Medical Affairs" } using stop
> The behavior I am looking for is getting back false whenever the text
> following ‘contains text' is reduced to an empty string. Is there a simple
> what of checking that?
Hm, sounds easy, but I don’t have an easy answer to that. We should
probably extend our ft:tokenize function to also take a
Hi Christian,
thanks a lot for your advice, but sorry, but I don't really get it so far.
Your code
> let $query := "Paris"
> for $city in doc('factbook')//city/name[text() contains text {$query}]
> return ft:mark($city)
doesn't return the 'mark'-tags, which are important for me and where
>> let $query := "Paris"
>> for $city in doc('factbook')//city/name[text() contains text {$query}]
>> return ft:mark($city)
>
> doesn't return the 'mark'-tags
Sorry, should have been like that:
let $query := "Paris"
for $city in doc('factbook')//city/name[text() contains text {$query}]
> …thanks for the hints. And sorry for the inconvenience; will be fixed soon.
http://files.basex.org/releases/latest/
On Sun, Jan 3, 2016 at 12:56 PM, Christian Grün
wrote:
>
>
> On Sat, Jan 2, 2016 at 11:09 PM, Andy Bunce wrote:
>> Using the
…thanks for the hints. And sorry for the inconvenience; will be fixed soon.
On Sat, Jan 2, 2016 at 11:09 PM, Andy Bunce wrote:
> Using the run button on /dba/queries seems broken for me in recent 8.4
> builds.
> Regardless of the query. The console shows: TypeError: Not
Hello,
A very happy new year to all of you !!!
I have some very basic questions with indexing.
1. Most of my xqueries are of below nature
'/Archives/descendant::apiCalls[contains(@name,"com.sun")]/@name', where
apiCalls could be 3-4 level under 'Archives'. Xqueries are accessed via REST
Based
Hi Christian,
my long-time project (kleist-digital.de) is nearly only based on documents
(TEI-xml), so I'm working mostly with mixed content. Are there any plans for
future versions to implement the ignore option for full-text-search? It would
help a lot.
Best,
Günter
17 matches
Mail list logo