Index by words seems broken in 2.5.3

[Pierre Rossel]

Hello,

> For CONTAINS search you need use SUBSTR()

What is the syntax using SUBSTR that will find records such as:

oranges
range

when looking for 'range' ?

With LIKE operator is: WHERE data LIKE '%range%'

It seems to me that with SUBSTR, you have to know where the data you search
is located in the word. Not with the LIKE operator.


> We have CHANGE this with LIKE specially.

What did you change ?
Why did you change it ?
I thought we where going to toward a stable 2.5.x release, so I don't
understand the point of changing the way things used to function until now.


> Because up to know LIKE was not able search phrases...

Is it able now ? Great! How ?


> Although its possible to control this by using Methods to have
>     a) normal index
>     b) index by words
> 
> We will discuss this here once more.

Yes, interesting. Maybe an article in the wiki could benefit everyone, with
the subject of multiple ways of searching data in text fields.

How to search a word in full text, the beginning of a word, a phrase...

In case it interests anyone, I have built the search engine of my app on the
LIKE operator for single words and the REGEX operator for phrases. One can
mix single words and phrases in the same query. This builds pretty complex
WHERE statements, but thanks to Valentina legendary speed, this is not a
problem. The syntax to use in my search field is inspired by the way Google
works. Multiple words are AND'ed and phrases are delimited by "". Words or
phrases are searched in defaults fields, but this can be overridden with a
prefix (example: a:doe searches in author field, t:apple searches in title
field...)

Pierre Rossel