Hello.
> Do I have to build an index first and how often is it updated etc? Yes, you should create FULLTEXT indexes. However I'm not sure if you will get any benefits for searching inner part of the words (*$key1*), because you can search using asterisk only on the left-most prefixes of the words. The performance of full-text searches some times is low, however it was improved in 5.1. Pluggable full-text parsers have appeared in this release as well. For a pity 5.1 is alpha quality now, and in most cases you shouldn't use it in a production environment. zzapper wrote: > Hi, > I've always done conventional searches Where ( title like '%$key1%') > or(isynopsis like '%$key2%') > etc etc > > But the client has increased the complexity of the search and especially the > size of his database > and the search has really slowed. (particularly now that I have to search a > longtext field.) > > So should I consider fulltext searching? > > Do I have to build an index first and how often is it updated etc? > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]