Hi,
Mroonga 9.01 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org
Hi,
Mroonga 9.00 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org
Hi,
Sorry, There was wrong release information in Mroonga 8.09.
The MySQL 8 is not supported. That is still being handled.
On 2018/11/29 14:12, Horimoto Yasuhiro wrote:
> Hi,
>
> Mroonga 8.09 has been released!
>
> Mroonga is a MySQL storage engine that supports fast fullte
Hi,
Mroonga 8.09 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org
Hi,
Mroonga 8.07 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org
Mroonga 8.06 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org/docs
Mroonga 8.03 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org/docs
Hi,
Mroonga 8.02 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org
Hi,
Mroonga 8.01 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org
Hi,
Mroonga 8.00 has been released!
This is a major version up! But It keeps backward compatibility.
You can upgrade to 8.0.0 without rebuilding database.
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
Hi,
Mroonga 7.11 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org
Hi,
Mroonga 7.10 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
* Document:
http://mroonga.org/docs/
* How to install:
http://mroonga.org/docs
Hi,
Mroonga 7.09 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org
Hi,
Mroonga 7.08 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org
Hi,
Mroonga 7.07 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org
Hi,
Mroonga 7.06 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org
Hi,
Mroonga 7.05 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org
Hi,
Mroonga 7.04 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org
Hi,
Mroonga 7.03 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org
Hi,
Mroonga 7.02 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org
Hi,
Mroonga 7.01 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org
Hi,
Mroonga 7.00 has been released! Even though major version upgrade, it
keeps compatibility of Mroonga database.
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document
Hi,
Mroonga 6.11 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org
:03, Kentaro Hayashi wrote:
>
> Hi,
>
> Mroonga 6.10 has been released!
>
> Mroonga is a MySQL storage engine that supports fast fulltext search
> and geolocation search. It is CJK ready. It uses Groonga as a storage
> and fulltext search engine.
>
> Document:
> ht
Can you post some benchmarks or comparison with elasticsearch?
Sent from ProtonMail mobile
Original Message
On 29 ott 2016 05:03, Kentaro Hayashi wrote:
Hi,
Mroonga 6.10 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and
Hi,
Mroonga 6.10 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org
Hi,
Mroonga 6.09 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org
Hi,
Mroonga 6.08 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org
Hi,
Mroonga 6.07 has been released!
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
How to install: Install Guide
http://mroonga.org
Hi,
Mroonga 6.06 has been released!
## What is Mroonga?
Mroonga is a MySQL storage engine that supports fast fulltext search
and geolocation search. It is CJK ready. It uses Groonga as a storage
and fulltext search engine.
Document:
http://mroonga.org/docs/
The characteristics of Mroonga
Hello all-
I have a question on searching via fulltext.
I have the following SQL statement:
var('SQLResultsID') = 'select *, MATCH
(product_id,product_name,product_desc) AGAINST("' + $sqlKeywordSearch + '") AS
SCORE from products WHERE MATCH (p
REE | |
> | FlightRoutes | 1 | ixRoutes | 1 | Dep |
> NULL | 1 | NULL | NULL | | FULLTEXT | |
> | FlightRoutes | 1 | ixRoutes | 2 | Des |
> NULL | 1 | NULL | NULL |
1 | ixRoutes |1 | Dep |
NULL | 1 | NULL | NULL | | FULLTEXT | |
| FlightRoutes | 1 | ixRoutes |2 | Des |
NULL | 1 | NULL | NULL | | FULLTEXT | |
| FlightRoutes |
ffect.
>
> Cheers
> Neil
>
> On Wed, Mar 31, 2010 at 5:29 PM, Mark Goodge wrote:
>
>> On 31/03/2010 16:52, Tompkins Neil wrote:
>>
>>> Hi
>>>
>>> I have the following fulltext search which appears to work fine for
>>> string
&g
>>
>> I have the following fulltext search which appears to work fine for string
>> phrases. However if I search like just "51" which is part of the string
>> name like 51 Blue Widget in the table it doesn't return any results.
>> However if I search like
On 31/03/2010 16:52, Tompkins Neil wrote:
Hi
I have the following fulltext search which appears to work fine for string
phrases. However if I search like just "51" which is part of the string
name like 51 Blue Widget in the table it doesn't return any results.
However if I sear
Hi
I have the following fulltext search which appears to work fine for string
phrases. However if I search like just "51" which is part of the string
name like 51 Blue Widget in the table it doesn't return any results.
However if I search like "bl" it returns the 51 Blue
Hi,
I'm currently working on a project which uses fuulltext searching. The
"with query expansion" feature is useful, but I was wondering if there's
any way to obtain the list of terms that the expanded query uses (other
than those originally input, of course). Is that possible, and, if so, how
didn't log anything to the permanent log. The
only trick about using my_printf_error was getting the header includes
correct -- I needed mysql/my_global.h first.
On Wed, Jul 15, 2009 at 7:09 PM, Tom Kleinpeter wrote:
> Hello,
>
> I've written a fulltext plugin for Mysql 5.1. The
Hello,
I've written a fulltext plugin for Mysql 5.1. The plugin works great
and I'm happy with it, but I would like to log an error when I
encounter some unexpected data. Do plugins have access to the Mysql
error log? If so, how do I write to it?
Thanks!
--
MySQL General Mailin
It looks perfect.
Thanks
Google for "myisam_ftdump", HTH Cor
- Original Message - From: "Sebastien Moretti"
To:
Sent: Thursday, April 23, 2009 5:24 PM
Subject: How to show highly frequent words in fulltext index ?
Hi,
Is there a command to see which words ar
Yes,
you can use myisam_ftdump
Bye
On Thu, 23 Apr 2009 17:24:09 +0200, Sebastien Moretti
wrote:
> Hi,
>
> Is there a command to see which words are highly frequent in a fulltext
> index ?
>
> Thanks
>
> --
> Sébastien Moretti
>
>
> --
> MySQL General
Hi,
Is there a command to see which words are highly frequent in a fulltext
index ?
Thanks
--
Sébastien Moretti
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Stefan,
On Sun, Mar 8, 2009 at 1:50 PM, Stefan Onken wrote:
> Hello,
>
> I am bit puzzled about combining mysql fulltext search into our
> current search:
>
> I am not able to combine a fulltext search with other selections,
> please see http://pastebin.com/m23622c39
Hello,
I am bit puzzled about combining mysql fulltext search into our
current search:
I am not able to combine a fulltext search with other selections,
please see http://pastebin.com/m23622c39 for full details. The
moment I am using "...where a=2 OR match (bla) AGAINST ('foo'
_unicode_ci.
> I have had the inverse problem and I solved with utf8_general_ci.
>
> Santino
>
> At 19:33 +0100 16-02-2009, Salam Baker Shanawa wrote:
> >Hi,
> >
> >How can I have accent sensitive, case insensitive fulltext query?
> >
> >version: 5.0.45
&
Hi,
try to set the collation to utf8_unicode_ci.
I have had the inverse problem and I solved with utf8_general_ci.
Santino
At 19:33 +0100 16-02-2009, Salam Baker Shanawa wrote:
Hi,
How can I have accent sensitive, case insensitive fulltext query?
version: 5.0.45
The database, tables
Hi,
How can I have accent sensitive, case insensitive fulltext query?
version: 5.0.45
The database, tables, connection, data etc. are all utf8.
select name from people where match(name) against ('"königsberger"' in
boolean mode);
shouldn't return konigsber
Can one make a composite index with FULLTEXT for one column and standard
indexing on another?
For instance we have a table
CREATE TABLE OurData
(
TheText TEXT,
TheLanguageID INTEGER
);
We have a FULLTEXT index on TheText, but want to be able to do searches
on TheText AND
Have you tried "in boolean mode"?
Santino Cusimano
At 16:30 -0500 20-11-2008, Little, Timothy wrote:
We are using MySQL 5.0.22 on CENTOS/redhat
linux. The table and database character-sets
are all utf8.
We have a database supporting numerous
languages. Of course, full-text works
beautifu
We are using MySQL 5.0.22 on CENTOS/redhat linux. The table and database
character-sets are all utf8.
We have a database supporting numerous languages. Of course, full-text works
beautifully with most of the languages.
But Chinese and Japanese are giving us problems, and there is NO reason
Hi all:
I am trying to build a FULLTEXT index with several particularities. It
must ignore some special characters inside index words. For example:
If I have the text:
I'll go to the ci[ne]ma.
I want the FULLTEXT include the word cinema, not ci[ne]ma nor ci or ne or
ma. So, I want the
> -Original Message-
> From: Ananda Kumar [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 13, 2008 10:48 AM
> To: [EMAIL PROTECTED]
> Cc: mos; mysql@lists.mysql.com
> Subject: Re: Fulltext index -first query slow, subsequent queries fast
>
> Hi
>
> Is sphi
Hi
Is sphinxsearch avialable only on for windows
regards
anandkl
On 6/13/08, Rory McKinley <[EMAIL PROTECTED]> wrote:
>
> mos wrote:
>
>
>> Why not switch to Sphinx full text search for MySQL? It is faster and can
>> handle more data than MySQL'
mos wrote:
Why not switch to Sphinx full text search for MySQL? It is faster and
can handle more data than MySQL's built in fulltext search.
http://www.sphinxsearch.com/
Mike
I have read about sphinx and the good performance boost it provides -
unfortunately there is a lot of legacy
At 02:20 PM 6/12/2008, you wrote:
Hi List
I have a table with a fulltext index across five fields, with about 2.2
million records and a data size of about 5.6 GB (index another 3.5 GB).
When I test a query that uses fulltext matching, the first run takes about
15-16 seconds to complete. The
>From: Rory McKinley [mailto:[EMAIL PROTECTED]
>Sent: Thursday, June 12, 2008 4:57 PM
>To: Jerry Schwartz; mysql
>Subject: Re: Fulltext index -first query slow, subsequent queries fast
>
>Jerry Schwartz wrote:
>> File system, or disk caching, uses some kind of algorithm to
system. The system might keep the
most recently used stuff, the most frequently used stuff, even the stuff it
thinks you will need based upon the pattern of use.
Regards,
Hi Jerry
Thanks for the explanation.
So, in short, I am most likely hitting a wall with the fulltext index,
and I am just
>-Original Message-
>From: Rory McKinley [mailto:[EMAIL PROTECTED]
>Sent: Thursday, June 12, 2008 3:20 PM
>To: mysql
>Subject: Fulltext index -first query slow, subsequent queries fast
>
>Hi List
>
>I have a table with a fulltext index across five fields, with
Hi List
I have a table with a fulltext index across five fields, with about 2.2
million records and a data size of about 5.6 GB (index another 3.5 GB).
When I test a query that uses fulltext matching, the first run takes
about 15-16 seconds to complete. The second run takes about 0.1 sec and
formatn command and if conditions, but still it take 3 min
>>
>
> Are you sure when you are running the fulltext search, the table isn't
> locked because you are building the index or altering the table?
>
> Mike
>
>
>
> select
>>
>>
>>
At 11:38 AM 6/12/2008, you wrote:
Hi Sebastian,
I tried to order the column as close as possible to the table structure and
removed all the formatn command and if conditions, but still it take 3 min
Are you sure when you are running the fulltext search, the table isn't
locked because yo
gt;
>>> Ananda Kumar schrieb:
>>>
>>>> Hi All,
>>>> We have table with 99 Million records, with fulltext index.
>>>> But when there is not load the sql's performance in just 6 sec, but when
>>>> anyother jobs like Index creation
On 6/12/08, Ananda Kumar <[EMAIL PROTECTED]> wrote:
>
>
>
> On 6/12/08, Sebastian Mendel <[EMAIL PROTECTED]> wrote:
>>
>> Ananda Kumar schrieb:
>>
>>> Hi All,
>>> We have table with 99 Million records, with fulltext index.
>>>
On 6/12/08, Sebastian Mendel <[EMAIL PROTECTED]> wrote:
>
> Ananda Kumar schrieb:
>
>> Hi All,
>> We have table with 99 Million records, with fulltext index.
>> But when there is not load the sql's performance in just 6 sec, but when
>> anyother jobs l
Ananda Kumar schrieb:
Hi All,
We have table with 99 Million records, with fulltext index.
But when there is not load the sql's performance in just 6 sec, but when
anyother jobs like Index creation or data load is happening its take close
to 3 min for the same query to execute, any wa
Hi All,
We have table with 99 Million records, with fulltext index.
But when there is not load the sql's performance in just 6 sec, but when
anyother jobs like Index creation or data load is happening its take close
to 3 min for the same query to execute, any ways to improve the performan
>Description:
copying a table with a fulltext index via
insert into ft1 select * from ft2;
into a identical table sometimes leads to select error 1191
when concurrent select's are running.
this happens in an enviroment where the searched
--- Lamp Lists <[EMAIL PROTECTED]> wrote:
>
> --- Lamp Lists <[EMAIL PROTECTED]> wrote:
>
> > hi,
> > I created table "tasks"
> > create table tasks(
> > task_id, int(4) not null primary key,
> > task text not null,
> > res
--- Lamp Lists <[EMAIL PROTECTED]> wrote:
> hi,
> I created table "tasks"
> create table tasks(
> task_id, int(4) not null primary key,
> task text not null,
> resolution text not null,
> fulltext (task, resolution)
> )engine=myisam
>
>
hi,
I created table "tasks"
create table tasks(
task_id, int(4) not null primary key,
task text not null,
resolution text not null,
fulltext (task, resolution)
)engine=myisam
when I run
seect * from tasks match(task,resolution)
against('"certain service"' in
starting point for finding that mistake Baron! :)
*knocks head against wall repeatedly*
On 10/30/07 5:09 PM, "Baron Schwartz" <[EMAIL PROTECTED]> wrote:
> Mike,
>
> Mike Morton wrote:
>> OK - I am at a total loss here :)
>>
>> We have added an addi
Mike,
Mike Morton wrote:
OK - I am at a total loss here :)
We have added an addition fulltext field with the highest rating:
match(search_keywords) against ('vic*' IN BOOLEAN MODE) * 16
And verified that in that field, there is indeed a keyword "vic" - but still
- that re
OK - I am at a total loss here :)
We have added an addition fulltext field with the highest rating:
match(search_keywords) against ('vic*' IN BOOLEAN MODE) * 16
And verified that in that field, there is indeed a keyword "vic" - but still
- that result is not returned, SO.
age-
> From: Mike Morton [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 30, 2007 9:56 AM
> To: Jerry Schwartz; mysql@lists.mysql.com
> Subject: Re: Fulltext Relevancy not returning anticipated results?
>
> Jerry:
>
> Sorry - I should have mentioned in my previous email that w
m: Mike Morton [mailto:[EMAIL PROTECTED]
>> Sent: Monday, October 29, 2007 5:39 PM
>> To: mysql@lists.mysql.com
>> Subject: Fulltext Relevancy not returning anticipated results?
>>
>> I have a database of products, doing a search on them trying to achieve
>> a
>>
mysql@lists.mysql.com
> Subject: Fulltext Relevancy not returning anticipated results?
>
> I have a database of products, doing a search on them trying to achieve
> a
> modicum of relevancy, but am getting a strange result on some returned
> rows:
>
> QUERY:
> select *
I have a database of products, doing a search on them trying to achieve a
modicum of relevancy, but am getting a strange result on some returned rows:
QUERY:
select *,match(code) against ('vic*' IN BOOLEAN MODE) * 8 + match(name)
against ('vic*' IN BOOLEAN MODE) * 4 + match(small_desc) against ('v
Justin wrote:
I'm wanting to add a new field to my table that I will both be
grouping by, searching with full text hits and plain likes..
I know I'll need a FULL TEXT index, but will that full text index
also index like a normal index will? or should I also add an index
too..
You'll need to ad
I'm wanting to add a new field to my table that I will both be grouping by,
searching with full text hits and plain likes..
I know I'll need a FULL TEXT index, but will that full text index also index
like a normal index will? or should I also add an index too..
thanks.
; Sent: Thursday, July 26, 2007 7:56 PM
> To: mysql@lists.mysql.com
> Subject: fulltext search option
>
> I'm having a problem with the fulltext searching, and was
> looking for some
> help.
>
> i'm currently working with the following query:
>
> select t
I'm having a problem with the fulltext searching, and was looking for some
help.
i'm currently working with the following query:
select table.*
from table where match(title, description) against ('*search term*' IN
BOOLEAN MODE)
the reason I am using boolean mode, is so th
Thank you for your information.
It's really helpful.:)
It seems that I'll have to dig deep into the fulltext search functionality.
2007/7/2, ViSolve DB Team <[EMAIL PROTECTED]>:
Hi,
There are some words which are drawn as "Stop words" [Words which are not
searchable
Hi,
There are some words which are drawn as "Stop words" [Words which are not
searchable in Fulltext Database]. To know the list of stopwords,
http://dev.mysql.com/tech-resources/articles/full-text-revealed.html.
"hello" is a stopword, and hence your query fails to
Steve Edberg wrote:
> At 11:23 PM +0800 6/30/07, Niu Kun wrote:
>
> To quote from
>
> http://dev.mysql.com/doc/refman/5.0/en/fulltext-search.html
>
>
> "... words that are present in more than 50% of the rows are considered
> common and do not match."
&
Octavian Rasnita wrote:
> Hi,
>
> Try:
>
> select * from test where match(name) against("hello" in boolean mode);
>
> Octavian
Thank you for your suggestion. I tried, but failed.:(
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.my
Hi,
Try:
select * from test where match(name) against("hello" in boolean mode);
Octavian
- Original Message -
From: "Niu Kun" <[EMAIL PROTECTED]>
To:
Sent: Saturday, June 30, 2007 6:23 PM
Subject: Problem about fulltext search.
Dear all,
I'm pla
At 11:23 PM +0800 6/30/07, Niu Kun wrote:
Dear all,
I'm planning to add fulltext search to my database.
I've got the following test command:
create table test(id int, name varchar(20));
alter table test add fulltext(name);
insert into test values(1,"hello world");
inser
Dear all,
I'm planning to add fulltext search to my database.
I've got the following test command:
create table test(id int, name varchar(20));
alter table test add fulltext(name);
insert into test values(1,"hello world");
insert into test values(1,"hello");
When
Hello
I've seen the posts of Nov 9 last year concerning the slow but steady
development of FULLTEXT indexes for InnoDB. Has this feature been
dropped or is it still being worked on?
My background: I'm working on a Rails project which needs fulltext
index search on the db layer.
pp Wabinski [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 20, 2007 9:31 AM
> To: mysql@lists.mysql.com
> Subject: fulltext substringsearches?
>
>
> Hi,
>
> can somebody tell me, if it`s possible to search for substrings with a
> fulltext search?
>
> We are using a f
Hi,
can somebody tell me, if it`s possible to search for substrings with a
fulltext search?
We are using a fulltextsearch in boolean mode. I tried a lot but the search
doesn`t find any substrings.
The mysql reference just hast got an example like this:
"apple*" that finds every
ge Global
Weight)
A) It is only an approximation, IT IS NOT accurate. Your mileage will
vary depending on the similarity of the contents of the two databases.
B) Get a second opinion on that.
Try it and let us know how well it works.
Regards,
Phil
> I've been using the MATCH(
I've been using the MATCH() with FullText Scoring for quite a while now on
one table. I now need to combine the data from another database. I have :
Database1.Table1
with
Database2.Table1
If I use the the FullText scoring using just one database/table it is OK,
but when I quer
ing before achieve
noticeably better results.
If you want I'd be happy to outline and expand on some ideas.
Regards,
Phil
It is more of an issue to prioritizing fields for relevance, and whether it
is possible to do this within a fulltext query, or whether it needs to be
done through
pened, the server was always shut
down properly.
-Andy
-Original Message-
From: Jerry Schwartz [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 01, 2007 4:10 PM
To: Andreas Iwanowski
Cc: mysql@lists.mysql.com
Subject: RE: Fulltext search dilemma (IN BOOLEAN MODE)
Sorry, I have no idea wh
1, 2007 2:22 PM
> To: Jerry Schwartz
> Cc: mysql@lists.mysql.com
> Subject: RE: Fulltext search dilemma (IN BOOLEAN MODE)
>
> Hi, thank you for your reply.
>
> I have used the option ft_min_word_len=3.
> If I have something like
> 1. "Key West"
> in the dat
[EMAIL PROTECTED]
Sent: Thursday, February 01, 2007 1:52 PM
To: Andreas Iwanowski; mysql@lists.mysql.com
Subject: RE: Fulltext search dilemma (IN BOOLEAN MODE)
Unless you changed the minimum word length, "Key" would be ignored
because it is too short. I would think the quotation marks at the
ington Ave.
Farmington, CT 06032
860.674.8796 / FAX: 860.674.8341
> -Original Message-
> From: Andreas Iwanowski [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 01, 2007 12:49 PM
> To: mysql@lists.mysql.com
> Subject: Fulltext search dilemma (IN BOOLEAN MODE)
>
&g
da
3. "Key West" Beach Florida
Now I do two fulltext searches on this column like this:
SELECT * FROM _my_table_here WHERE MATCH(Keywords) AGAINST ('*Key*
*West*' IN BOOLEAN MODE)>0;
SELECT * FROM _my_table_here WHERE MATCH(Keywords) AGAINST ('*Miami*
*Beach*' IN
1 - 100 of 1232 matches
Mail list logo
