http://www.icyphoenix.com/viewtopic.php?f=4&t=2520&p=26470#p26470
-----------------------------------
moreteavicar
Wed 19 Mar, 2008 03:12

Re: Mysql Errors Solution While Installing
-----------------------------------
I suspect the tables here are a bit out of date now, but I thought I'd point out something. In the InnoDB script given above, all that has been done is to put TYPE=InnoDB at the end of each table. How does this actually solve the problem of a full text table index on MS servers? 

Look for instance at:

[code linenumbers=false]CREATE TABLE `phpbb_hacks_list` (
  `hack_id` mediumint(8) unsigned NOT NULL auto_increment,
  `hack_name` varchar(255) NOT NULL default '',
  `hack_desc` varchar(255) NOT NULL default '',
  `hack_author` varchar(255) NOT NULL default '',
  `hack_author_email` varchar(255) NOT NULL default '',
  `hack_author_website` tinytext NOT NULL,
  `hack_version` varchar(32) NOT NULL default '',
  `hack_hide` enum('Yes','No') NOT NULL default 'No',
  `hack_download_url` tinytext NOT NULL,
  `hack_file` varchar(255) NOT NULL default '',
  `hack_file_mtime` int(10) unsigned NOT NULL default '0',
  PRIMARY KEY  (`hack_id`),
  UNIQUE KEY `hack_name` (`hack_name`),
  KEY `hack_file` (`hack_file`),
  KEY `hack_hide` (`hack_hide`)
)TYPE=InnoDB;[/code] 
hack_name and hack_file are still both text keys...  so nothing has been done to change the indexes that are used - where there are text indexes in the MYISAM tables, they remain text indexes in INNODB tables, surely this will cause the same "The used table type doesn't support FULLTEXT indexes" error...

I also don't think "multiple database users" is the reason MYISAM was dropped - since most MYSQL servers assign MYISAM by default! If you wanted to avoid MYISAM, your won't get round it by not declaring an alternative engine. (Perhaps that was what MG had in mind, or perhaps the fact that "TABLE" is deprecated, and was going to replace with "ENGINE"?). 

Interesting note - MYSQL supports hyper-threading regardless of engine, and in fact in a number of cases MYISAM scales the better with multiple threads than InnoDB ([url=http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/]See here), even if slower in some other cases (contrary to rumour that most people think MYISAM is the fastest of the disk engines, the truth is a lot more subtle - it depends largely on the sort of queries you're most likely to make). 

Perhaps we should just use HEAP engines  :mrgreen: