Hi!
On May 23, Przemyslaw Popielarski wrote:
Sergei Golubchik [EMAIL PROTECTED] wrote:
It looks like a bug. Can you create a test case for this ?
create table tBooks (
isbn char(10) not null primary key,
title varchar(60) not null,
fulltext index (title)
);
insert into tBooks
Sergei Golubchik [EMAIL PROTECTED] wrote:
1 row in set (0.00 sec)
Works fine for me (that is No rows - and no bug).
Probably, it's one of numerous fulltext-related bugs that were fixed
since 4.0.1 release.
Will you fix it in 3.23.x ? There is still lot of time (I think) to
release 4.x
Przemyslaw,
Wednesday, May 22, 2002, 2:02:52 AM, you wrote:
PP SELECT ISBN,TITLE FROM tBooks
PP WHERE tBooks.ISBN=1876340436
PP AND MATCH (tBooks.TITLE) AGAINST (britannica)
PP ++-+
PP | ISBN | TITLE |
PP
Hi!
On May 22, Victoria Reznichenko wrote:
Przemyslaw,
Wednesday, May 22, 2002, 2:02:52 AM, you wrote:
PP SELECT ISBN,TITLE FROM tBooks
PP WHERE tBooks.ISBN=1876340436
PP AND MATCH (tBooks.TITLE) AGAINST (britannica)
PP ++-+
PP | ISBN |
Sergei Golubchik [EMAIL PROTECTED] wrote:
It looks like a bug. Can you create a test case for this ?
create table tBooks (
isbn char(10) not null primary key,
title varchar(60) not null,
fulltext index (title)
);
insert into tBooks (isbn,title) values
('1876340436','2000 Lonely Planet
This simply can't be correct - if a match produces 0 score (no
relevance), the whole condition part after AND in this example could
be reduced to 0 (=FALSE), hence the query *should* produce 0
records:
SELECT ISBN,TITLE FROM tBooks WHERE tBooks.ISBN=1876340436 AND 0;
...and here is a real-life
SELECT ISBN,TITLE FROM tBooks
WHERE tBooks.ISBN=1876340436
AND MATCH (tBooks.TITLE) AGAINST (britannica)
++-+
| ISBN | TITLE |
++-+
| 1876340436 | 2000 Lonely Planet Calendar |
