UBB.threads PHP Forum Software Community Forums UBB.threads 7 Bug Reports Non Bugs [NOTABUG] dosearch.inc.php

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.

I can't believe any host is still using mysql 3

Wow -- learn something new everyday.

I would be concerned about hosts that do this since they may not be patching the server software to the latest versions and you might have a whole bunch of security holes just waiting to be exploited.

IMHO -- UBBThreads needs to take advantage of features the majority of users will benefit from -- If this loses users who are using mySQL 3 maybe they need to stay with an old version of the forum for the old version of mySQL.

No offense meant to anyone just an interesting topic

a lot of hosts do it, some list them as legacy servers and leave it for users that don't know any better; gives them a way to charge you a maintenance/upgrade/migration fee when you complain...

I think you miss-understood my point though...

I have no problem, and in fact would love to upgrade to 4 or maybe even 5... But with core3 i can't.. I would have to upgrade my whole server OS to core4 or 5 at least to run sql 4 minimum.

My server runs a lot more sites than just this one, and i have seen server upgrades screw up a lot of tihngs in the past, so I am a bit gun shy of doing this just for the sake of running sql4 for this one site.

Why would you have to upgrade to core4 or core5? An upgrade in MySQL or any other system service don't require an entire server ugprade; just because the yum repository for your cpanel or distro doens't have a precompiled binary doesn't mean you can't upgrade the services...

True enough I suppose. Been down that road before though. I guess I get a bit cosy with yum because it handles all the dependancies etc very easily. Its a larger exercise doing it all by hand for sure. (And risking things breaking for a slightly but not fully familiar user of linux like myself.)

True, YUM does do a good job of auto-upgrading things; but if you'll notice its often many versions behind (for instance, I use YUM to upgrade my PHP4 install, the latest in the CENTOS repo is 4.3.9 wheras the latest in the 4.0 tree is 4.4.4)

An interesting thought I had, I'm not sure if YUM is capable of upgrading "major revisions" (as in from 4.x to 5.x); I say this meerely because I have several services installed that have version conventions like this however it doesn't upgrade them (such as PHP or even MySQL); likely theres an option somewhere, that or it'll just treat it as a new service (which would be bad)

I've been doing a lot of reading on this upgrade.. It seems there are some things I need to do to convert my DB's... ISAMS etc etc etc...

Kind of off topic, but if i back up all my db's then set up ver4 or ver5 then set up new DB's and restore the backed up data into those new DB's would that work as well?

Again sorry, i know this isnt a mysql support site

Same question here, Is it safe to update to a new Mysql version for a complete box?

Clicky Click May help ?

I've had no problems in upgrading MySQL; however you may with some systems that use a control panel such as Ensim, Plesk, or CPanel, in which you should check their site for how to upgrade.

Well did the upgrade myself. Although it is not so easy, use the following resources to let it work. Just updated two boxes to the new MySQL. The real reason why MySQL 3 is still installed is:

http://forum.ensim.com/showthread.php?t=15583
http://onlinesupport.ensim.com/TWKB/ViewCase.asp?RuleID=2001&QSCatid=0&CurrentPage=1&QSKeyword=mysql~upgrade&QSUpdateUsage=yes
http://dev.mysql.com/downloads/mysql/4.1.html

The RPM's for 4.0 which need to be installed first:
MySQL-server-4.0.27-0.i386.rpm
http://dev.mysql.com/get/Downloads/MySQL-4.0/MySQL-server-4.0.27-0.i386.rpm/from/http://mysql.he.net/
MySQL-client-4.0.27-0.i386.rpm
http://dev.mysql.com/get/Downloads/MySQL-4.0/MySQL-client-4.0.27-0.i386.rpm/from/http://mysql.he.net/
MySQL-devel-4.0.27-0.i386.rpm
http://dev.mysql.com/get/Downloads/MySQL-4.0/MySQL-devel-4.0.27-0.i386.rpm/from/http://mysql.he.net/
MySQL-shared-4.0.27-0.i386.rpm
http://dev.mysql.com/get/Downloads/MySQL-4.0/MySQL-shared-4.0.27-0.i386.rpm/from/http://mysql.he.net/
MySQL-shared-compat-4.0.27-0.i386.rpm
http://dev.mysql.com/get/Downloads/MySQL-4.0/MySQL-shared-compat-4.0.27-0.i386.rpm/from/http://mysql.he.net/