[support] Full-text data search in InnoDB tables

[Jamie Holly]

Yup, MyISAM is your only option and you can do just that one table.

For misspelled words, you need a different search solution like SOLR.

Jamie Holly
http://www.intoxination.net
http://www.hollyit.net

On 8/27/2012 8:43 PM, Kamal Palei wrote:
> HI Jamie Holly
> Thanks for information.
> So, probably I should have that particular table as myisam now, later 
> convert it to innodb.
> By the way, how people acheive searching of wrong spelt words (example 
> if I type wrong spelt word in google search field).
> Regards
> Kamal
>
>
> On Tue, Aug 28, 2012 at 6:06 AM, Jamie Holly 
> <hovercrafter at earthlink.net <mailto:hovercrafter at earthlink.net>> wrote:
>
>     MySQL's full text support for InnoDB is highly new. You have to be
>     running MySQL 5.6.4+. MySQL 5.6 is still in dev, so unless you are
>     on a dedicated server, VPS or Cloud and want to get really risky
>     with your data, you are going to have to wait.
>
>     Jamie Holly
>     http://www.intoxination.net  <http://www.intoxination.net/>  
>     http://www.hollyit.net  <http://www.hollyit.net/>
>
>     On 8/27/2012 8:30 PM, Kamal Palei wrote:
>>     Hi Ursula
>>     Thank for reply.
>>     I know with 'like' query will work.
>>     But you know, 'like' is not preferred from perfroamance
>>     perspective as well sometimes it may not give expected result
>>     (example %man% may return "woman" etc..).
>>     I am looking at if somebody enters words with minor spell
>>     mistake, still our search should pick the right word.
>>     Lets say in my table, I have a key word "session initiation
>>     protocol". If somebody searches "sesson initiaton protocol",
>>     still I should be able to pick the right key word.
>>     To acheive above, there should be some way out, since me a newbie
>>     in database just was looking how experts do these with innodb tables.
>>     Best Regards
>>     Kamal
>>     NECS, Bangalore
>>
>>     On Tue, Aug 28, 2012 at 5:51 AM, Ursula Pieper
>>     <dramamezzo at gmail.com <mailto:dramamezzo at gmail.com>> wrote:
>>
>>         Hi Kamal,
>>
>>         Did you try the following query:
>>
>>         select * from resubmt_skill_ids where name like "%java%";
>>
>>         Did  I understand you correctly, and this is what you are
>>         looking for?
>>
>>         Ursula
>>
>>         On Mon, Aug 27, 2012 at 5:43 AM, Kamal Palei
>>         <palei.kamal at gmail.com <mailto:palei.kamal at gmail.com>> wrote:
>>
>>             Hi All
>>             I am using Drupal 6.26, MySql (innodb).
>>             I tried to first to do full text data search in InnoDB table.
>>             A simple query statement is shown as below.
>>             *SELECT * FROM resubmt_skill_ids WHERE MATCH (name)
>>             AGAINST ('java')*
>>             But I get the below error.
>>             #1214 - The used table type doesn't support FULLTEXT indexes
>>             On further google search, came to know, only MyISAM type
>>             tables support full-text search.
>>             I am bit reluctant to change my tables from InnoDB to
>>             MyISAM.
>>             Can somebody suggest me is it not possible to do
>>             full-text search in InnoDB tables.
>>             Came across
>>             http://blogs.innodb.com/wp/2011/07/innodb-full-text-search-tutorial/ have
>>             not gone completely, but it looks author tells full-text
>>             search possible with innodb tables.
>>             If anybody has used full-text search on innodb tables,
>>             please let me know, how to do that from drupal perspective .
>>             Best Regards
>>             Kamal
>>             NECS, Bangalore
>>
>>             --
>>             [ Drupal support list | http://lists.drupal.org/ ]
>>
>>
>>
>>         --
>>         [ Drupal support list | http://lists.drupal.org/ ]
>>
>>
>>
>>
>
>
>     --
>     [ Drupal support list | http://lists.drupal.org/ ]
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20120827/c404be86/attachment.html