User warnings: table doesn't support/table doesn't exist
daneesia - August 11, 2007 - 11:39
| Project: | UIE Forum |
| Version: | 5.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
I just downloaded the August 11 version of UIE forum (after un-installing/deleting the August 9 version) and I received the following error when enabling the module:
user warning: The used table type doesn't support FULLTEXT indexes query: CREATE TABLE `F_Posts` ( `PostID` int(12) NOT NULL auto_increment, `PostTitle` varchar(255) default NULL, `ThreadID` int(8) NOT NULL default '0', `Poster` int(8) NOT NULL default '0', `Posted` int(11) NOT NULL default '0', `Content` text NOT NULL, `Edit` int(11) NOT NULL default '0', `Editor` int(8) default NULL, `EditReason` varchar(255) default NULL, PRIMARY KEY (`PostID`), KEY `ThreadID` (`ThreadID`), KEY `Poster` (`Poster`), KEY `Posted` (`Posted`), FULLTEXT KEY `SearchFields` (`PostTitle`,`Content`) ) DEFAULT CHARACTER SET UTF8; in C:\mypath\database.mysql.inc on line 172.Next I am receiving errors when creating threads (which I suppose makes sense based on the above):
user warning: Table 'mydatabasename.f_posts' doesn't exist query: INSERT INTO F_Posts (PostID, PostTitle, ThreadID, Poster, Posted, Content) VALUES (NULL,'my new thread','3','1','1186831367','bla') in C:\mypath\database.mysql.inc on line 172.
user warning: Table 'mydatabasename.f_posts' doesn't exist query: SELECT * FROM F_Posts LEFT JOIN users ON F_Posts.Poster = users.uid WHERE ThreadID=3 ORDER BY PostID ASC LIMIT 0, 25 in C:\mypath\database.mysql.inc on line 172. Oh and for the record I am using Drupal 5.1 & MySQL 5
#1
The only thing I can think of with this being a bug uieforum is the ") DEFAULT CHARACTER SET UTF8" part in uiforum.install creating the tables. That line should really look like
) /*!40100 DEFAULT CHARACTER SET UTF8 */;");
but 2 tables got it wrong on last update. I know zoro have comitted this fix to cvs but it may still take a few hours before a new dev release is roled out. So if you like to test this, in uieforum.install replace the 2 instances that just have
) DEFAULT CHARACTER SET UTF8");
with
) /*!40100 DEFAULT CHARACTER SET UTF8 */;");
or wait for an updated dev release. THis fix is mostly for compability between different versions of mysql and shouldnt play a role here.
Instead I would recommend you to update drupal to 5.2, because it has several bug as well as security fixes, and it may as well be where the problem is and not in uieforum. Actually I think that's the case, because I tested to install the same release w/o any db problems and I use mysql 5 too, and php 5.2.3 (maybe your php is old or a buggy version?).
#2
I have now tested the very latest commit and it works as expected. However, I notice you are running it on Windows and that may be related to it. The error message quite clearly say that "FULLTEXT indexes" not supported, and this may have to do with your version of mysql or php, and/or windows, or any configuration of these.
#3
If you read the message very carefully, it says "The used table type doesn't support Fulltext", which makes me believe everything on my end is fine (thus the bug).
Note: I did NOT receive this warning when installing the August 9 version (again, thus the bug)
I am using the latest stable versions of everything (except Drupal because too many Modules have not yet been updated and I am quite sure not everyone has jumped on the 5.2 bandwagon yet:
MySQL 5.0.45
PHP 5.2.3
Apache 2.2.4
Windows XP SP2
#4
Ok I think I have tracked it, "Table type" is DEFAULT, so what is your default table type in mysql (look at my.conf)? I think the reason can be you have it set to InnoDB and not MyISAM which can cause this. InnoDB doesn't support FULLTEXT index, at least not in mysql 5.0 and if there isn't any special reason for it I can't see why you should run it as InnoDB?
Otherwise, your versions as such seem ok, except I don't agree about Drupal 5.2, as faik there are no module incompatibility issues between 5.1 and 5.2, modules updated to 5.x should work in 5.1 as well as 5.2, but there might be a bug in 5.1 that break newer things, I don't know. You are running this on your local computer or how is the whole thing setup?
#5
And that's why I had set the MyISAM in the install file :)
#6
Yes I see that now ;-) However, MyISAM is the mysql default so it shouldn't be needed AND if users changes that they are supposed to know what they are doing - or they simply have to learn it the hard way :-)
#7
OK, I am now using Drupal 5.2 and am no longer recieving the user warnings.
Setting this to closed.
Thanks.