Hi,

were runing 7.0Beta4 and have the following problem in the search :

Script: /home/httpd/vhosts/satboard.nl/httpdocs/forum/scripts/dosearch.inc.php
Line#: 566
SQL Error: You have an error in your SQL syntax near 'BOOLEAN MODE) OR MATCH t1.POST_BODY AGAINST ('sadb' IN BOOLEAN M' at line 9
SQL Error #: 1064
Query: SELECT t1.POST_ID FROM ubbt_POSTS as t1, ubbt_TOPICS as t2 WHERE t1.POST_IS_APPROVED = '1' AND t2.TOPIC_STATUS <> 'M' AND t2.FORUM_ID IN ('1','2','3','4','5','6','7','8','9','10','11','12','13','14','15','16','17','18','19','20','21','22','23','24','25','26','27','28','29','30','31','32','35') AND t1.TOPIC_ID = t2.TOPIC_ID AND (MATCH t1.POST_SUBJECT AGAINST ('sadb' IN BOOLEAN MODE) OR MATCH t1.POST_BODY AGAINST ('sadb' IN BOOLEAN MODE)) AND t1.POST_POSTED_TIME > '1157309154' ORDER BY t1.POST_POSTED_TIME DESC LIMIT 200

Gebruik de 'Backspace' knop om terug te gaan.

Any ideas ?

Regards

does anybody has an idea what is wrong ? please need help with this? or will it be solved by the new beta 5 ?

When will it be online?

Regards

What version of MySQL are you currently running? This SQL query runs ok on here and my test box. It looks like perhaps you're using an older version of MySQL that doesn't support fulltext boolean mode?

im using:

mysql 3.23.58-16.RHEL3.1

It runned wel on the previous versions 7..

Ok, in order for everything to work you'll need to be running MySQL version 4 at the minimum. The majority of things will work under MySQL 3 but it doesn't fully support everything that version 7 needs, so MySQL 4 will be the minimum required.

okay thanxs, i will try to upgrade mysql


Regards

Ok, so... Then in saying this, you are also saying that I will need to update my whole server machine to something higher than core3?

Searching yum, it says the latest upgrades to mysql is 3.23.58-16.FC3.1

I am sure you guys can appreicate the magnatude of having to update and mess with my server just because of this new way of searching the forums?

Couldnt this have been done some other way so it would be somewhat backward compatible? Doesnt seem right to do it that way and cause so many people these issues? Specially when it worked before the other way.

Keep in mind that the current version of MySQL is in the 5.x versions, 4.x which has been out for several years and over time certain features and functionality has been added; it doens't seem to be asking too much for how certain portions of MySQL work currently... Having to cut back from features in the current versions to support legacy versions is asking a lot, and I think that MySQL3 shouldn't be a logical step to have 110% support for..

Then why are there still shared servers using MySql 3 if MySql 4 has been out for several years?

because its cheap to sell an old retired server again. Old mashines that are replaced by new one and sold to a low cost provider.