I'm obviously getting myself into more and more trouble with fulltext..
I have the following SQL statement;
SELECT indexIdentity, webpageIdentity, content, MATCH (content) AGAINST
('gallery' ) as score FROM db_com_pacificmomentum.tbl_index
where MATCH (content) AGAINST ('gallery' );
Which retur
Hello,
I tried the FULLTEXT example from the manual
(http://www.mysql.com/doc/F/u/Fulltext_Search.html) and run across some
problems. On some search terms, I get a result set and others I do not.
The query -> SELECT * FROM articles WHERE MATCH (title,body) AGAINST
('database') returns a result,
Hi!
On Feb 19, Alexander Belyaev wrote:
>
> Hello,
>
> Sergey, thanks for the patch, I applied it for 4.0.1 and seems like
> mentioned bug closed.
>
> But I found new bug :)
>
> Strange, but the query WORKS AS EXPECTED without fulltext index!
>
> The results for 4.0.1 with latest fulltext p
Hello,
Sergey, thanks for the patch, I applied it for 4.0.1 and seems like
mentioned bug closed.
But I found new bug :)
Strange, but the query WORKS AS EXPECTED without fulltext index!
The results for 4.0.1 with latest fulltext patch applied:
If you need full testcase, please conteact me.
Hi!
On Feb 02, Alexander Belyaev wrote:
> Hello,
>
> I have found a bug( or bad feature? :) ) in 4.0.1
> boolean fulltext search
>
> Please help...
>
> --
> select id,txt from test.logo_text where match(txt) against ('+desig*
> +service' in boolean mode)
> --
> 2 rows i
Hi!
> "Alex" == Alex Aulbach <[EMAIL PROTECTED]> writes:
Alex> I found out, that the fulltext engine is misbehaving with less than 5
Alex> entries. Seems to me, that this is exactly the same case...
Alex> Perhaps a flush inside the engine or so isn't made with such less entries?
Alex> The
Date: Sat, 2 Feb 2002 11:41:36 +0300
From: Alexander Belyaev <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Fulltext problems 4.0.1 part two
Hello,
I have found a bug( or bad feature? :) ) in 4.0.1
boolean fulltext search
Please help...
Test case with table can be found at http://l
Hello,
I have found a bug( or bad feature? :) ) in 4.0.1
boolean fulltext search
Please help...
Test case with table can be found at http://logo.nino.ru/fulltextbug.tar.gz
Alexander
( "sql database query table" for you, spam protector:)
--
show variables like 'ft%'
-
Hello,
Why score is 0 in my query?
Any suggestions? Seems like fulltext '*' operator produce buggy results.
Alexander
>>>
mysql> \s
--
./mysql Ver 11.19 Distrib 4.0.1-alpha, for pc-solaris2.8 (i386)
Connection id: 9
Current database:
Curr
Hello
> > The error says: "Can't read indexpage from filepos: -1". [...]
>
> Thank you for reporting this. This will be fixed in a next release.
> But it was really not a big problem - the table was not really
> corrupted. [...]
Thanks for the fix and the explanation!
cheers
--
TS
-
Hi!
Sorry for delay :-(
On Jan 24, Tibor Simko wrote:
> Hello
>
> I wrote:
>
> > > After upgrading to 3.23.31, FULLTEXT selects give often "error -1
> > > from table handler" for me. [...]
>
> Sergei Golubchik <[EMAIL PROTECTED]> wrote:
>
> > Thanks for a bug report! This would be fixed in
Hello
I wrote:
> > After upgrading to 3.23.31, FULLTEXT selects give often "error -1
> > from table handler" for me. [...]
Sergei Golubchik <[EMAIL PROTECTED]> wrote:
> Thanks for a bug report! This would be fixed in a nex release.
Thanks. In 3.23.32 the test case I submitted apparently wo
Hi!
On Jan 19, Tibor Simko wrote:
> Hello
>
> After upgrading to 3.23.31, FULLTEXT selects give often "error -1 from
> table handler" for me. The error log says "ft_read_first: Got error
> -1 when reading table foo". I think I have not seen those for older
> 3.23.x versions (x=28 or so), at le
Hello
After upgrading to 3.23.31, FULLTEXT selects give often "error -1 from
table handler" for me. The error log says "ft_read_first: Got error
-1 when reading table foo". I think I have not seen those for older
3.23.x versions (x=28 or so), at least not that frequently.
A small example to re
14 matches
Mail list logo
