List:General Discussion« Previous MessageNext Message »
From:Arthur Fuller Date:November 19 2002 5:38pm
Subject:RE: InnoDB != FULLTEXT?
View as plain text  
In the meantime, Jan, you don't have to commit your whole database to one
table type. Consider using MyISAM tables where you need fulltext search and
InnoDB for your other data.

Arthur

-----Original Message-----
From: Heikki Tuuri [mailto:Heikki.Tuuri@stripped]
Sent: Tuesday, November 19, 2002 12:02 PM
To: mysql@stripped
Subject: Re: InnoDB != FULLTEXT?


Jan,

----- Original Message -----
From: "Jan Steinman" <Jan@stripped>
Newsgroups: mailing.database.mysql
Sent: Tuesday, November 19, 2002 4:37 AM
Subject: InnoDB != FULLTEXT?


> I'm interested in using InnoDB, but am loathe to give up FULLTEXT
indexing.
>
> Anyone (Heikki?) know why this is so, and if it is likely to be changed in
the future?

there is no technical hinder in porting fulltext indexes on top of InnoDB.
But so far, the demand from commercial customers has not been enough to
assign the resources for it. The port is in the long-term goals of the
InnoDB TODO list.

> --
> ---- SQL SQL SQL SQL SQL SQL SQL SQL  ----
> : Jan Steinman -- nature Transography(TM): <http://www.Bytesmiths.com>

Best regards,

Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, row level locking, and foreign key support for MySQL
See http://www.innodb.com, download MySQL-Max from http://www.mysql.com




---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <mysql-thread125311@stripped>
To unsubscribe, e-mail <mysql-unsubscribe-afuller=etsys.com@stripped>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php



Thread
InnoDB != FULLTEXT?Jan Steinman19 Nov
Re: InnoDB != FULLTEXT?Heikki Tuuri19 Nov
  • RE: InnoDB != FULLTEXT?Arthur Fuller19 Nov