Hi all, At the moment, we all know that InnoDB does not yet have FULLTEXT indexes. This is not another message asking as to when we will have that functionality.
This message is different. On the mailing list for DBMail, we've been discussing MySQL table types, with everyone highlighting the fact that MyISAM does not support transactions while InnoDB does (in addition to foreign keys). Then, I raised the point that MyISAM may not have transactions, but it does have FULLTEXT indexes, which could be a massive source of speed for MyISAM-based tables. My question is this: Obviously, if you throw SQL statements enclosed in BEGIN/COMMIT and issue ROLLBACK statements on MyISAM tables, MyISAM does the right thing and ignores it (personally, I think it would be better if it alerted the nearest admin, so that they could come and deal with any person touching their finely tuned database server). Is the converse-ish statement true? Is there any way that FULLTEXT searches could be executed on InnoDB (and other type) tables currently or with a quick patch that uses a full table scan? I'd be willing to get together with a few people to write such a thing, as it would speed development while FULLTEXT is a MyISAM exclusive while still allowing testing against all MySQL tables in the immediate future. Regards, Chris -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
