[ciapug] Search tool

[Carl Olsen]

I see I'm going to have to duplicate some of my data into MyISAM tables to
get full text index searching.  It looks like PostgreSQL would be a better
solution.

--
Carl Olsen, MCSE
Web Developer, CMS Implementation
Marketing and Communications
Drake University
2507 University Avenue
115 Old Main
Des Moines, Iowa 50311-4505
Phone: 515-271-2986
Fax: 515-271-3798
Carl.Olsen at drake.edu
www.drake.edu

-----Original Message-----
From: ciapug-bounces at cialug.org [mailto:ciapug-bounces at cialug.org] On Behalf
Of Carl Olsen
Sent: Friday, July 21, 2006 3:37 PM
To: ciapug at cialug.org
Subject: RE: [ciapug] Search tool

Now that I have my search string function written, I'm looking at the
FULLTEXT search in MySQL.  The first thing I notice is that it wants the
data in MyISAM and I have mine in InnoDB.  I haven't gotten very far as far
as actually stuffing data in my tables yet, so I could easily switch to
MyISAM at this point.  I think the only thing I'm using InnoDB for is
foreign keys and cascading deletes which I could easily move to my PHP data
functions.  I haven't started reading much about FULLTEXT searches yet, but
I did notice a few people creating separate tables and temporary tables for
faster searching.  I've done something like that before to improve the speed
of a search.  Does anyone have any suggestions on best practices with MySQL
FULLTEXT searches?