two possible orders in fulltext.test

>Description:
These queries have results with the same relevance:
select * from t1 where MATCH(a,b) AGAINST ("collections");
select * from t1 where MATCH(a,b) AGAINST ("collections") UNION ALL
select * from t1 where MATCH(a,b) AGAINST ("indexes");

MySQL can choose any order for returning the results. If the internal
data structure changes, the .result file becomes invalid. This happend
with the above queries.

>How-To-Repeat:
cd mysql-test
../mysql-test-run --do-test=fulltext

>Fix:
Add "order by a" to the queries to have an explicit result order (and
change the .result file accordingly).

>Originator: Julian Ladisch
>MySQL support: licence
>Synopsis: two possible orders in fulltext.test
>Severity: non-critical
>Priority: low
>Category: mysql
>Class: sw-bug
>Release: mysql-4.0.4-beta (Source distribution)
>Environment:
System: Linux 2.4.10-4GB #1 i686
Compilation info: CC='gcc' CFLAGS='-O3' CXX='gcc' CXXFLAGS='-O3 -felide-constructors -fno-exceptions -fno-rtti' LDFLAGS=''
Configure command: ./configure --prefix=/usr/local/mysql --enable-assembler --with-mysqld-ldflags=-all-static CFLAGS=-O3 'CXXFLAGS=-O3 -felide-constructors -fno-exceptions -fno -rtti' CXX=gcc


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12645@lists.mysql.com
To unsubscribe, e-mail

Re: two possible orders in fulltext.test

Hi!

On Oct 07, Julian Ladisch wrote:
> >Description:
> These queries have results with the same relevance:
> select * from t1 where MATCH(a,b) AGAINST ("collections");
> select * from t1 where MATCH(a,b) AGAINST ("collections") UNION ALL
> select * from t1 where MATCH(a,b) AGAINST ("indexes");
>
> MySQL can choose any order for returning the results. If the internal
> data structure changes, the .result file becomes invalid. This happend
> with the above queries.

Yes, but internal data structures didn't change, and fulltext.test
works fine for me.

So - I failed to repeat the bug.

Regards,
Sergei

--
MySQL Development Team
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/
/_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany
<___/

------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12661@lists.mysql.com
To unsubscribe, e-mail

Re: two possible orders in fulltext.test

> > These queries have results with the same relevance:
> > select * from t1 where MATCH(a,b) AGAINST ("collections");
>
> So - I failed to repeat the bug.

You are right. I undefined COMPILE_STOPWORDS_IN in myisam/ftdefs.h, no
wonder that the result changes. fulltext.test is the only test affected by
the stopword list.

Julian


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12665@lists.mysql.com
To unsubscribe, e-mail