I was attempting to use swishe for an index, but it could not handle the
70+GB of data that I needed it to.  MySQL does handle that, and it has nice
querying capabilities.  It is considerably slower, but not too bad in most
cases(only 1-3 seconds usually).  Since I've been using it though my Linux
box has had nothing but troubles with its SCSI  driver.  I think I might be
going back to glimpse -- it has bugs and many limitations, but it works
reliably and it can handle the data I need it to.  I'm looking forward to
when 64-bit swishe comes out though!

-----Original Message-----
From: Peter Karman [mailto:karman@cray.com]
Sent: Thursday, December 11, 2003 2:16 PM
To: Multiple recipients of list
Subject: [SWISH-E] mysql and swishe


I'm hoping for some feedback from swish-e users out there who are also 
using mysql.

I know that some folks use swish-e to index mysql tables for searching. 
Is there a reason you do that instead of just querying the database 
directly? Is there a big performance difference?

I am just starting to research a significant mysql project and haven't 
used it before. I've toyed off and on with using swish-e as the backend 
instead of mysql, but that seems to be advantageous only for read-only 
searching, not doing any kind interaction that would require saving data.

Horror/success stories welcome.

pek
-- 
Peter Karman - Software Publications Engineer - Cray Inc
phone: 651-605-9009 - mailto:karman@cray.com