0 Replies Latest reply on Jul 24, 2009 3:24 PM by cpthk0

    verity search vs mySQL FULL-TEXT search

    cpthk0

      Hi:

       

      I am building a website that does some search. My datas are simple words like names, brand name... instead of some paragraphs and articles. All my datas are stored in mySQL.(I still can re-import them into verity engine if I plan to go with verity, that's not a issue here.) I was wondering which approach is better, verity search build-in CF or mysql.

       

      Here are some pros and cons:

      mySQL

      pros:

      1. my data has to be stored in mySQL, so if I go with verity search, I will have to design my code to import data into both verity engine AND mySQL, which is pretty awkward to me. Why one data send to two databases?

       

      cons:

      1. mySQL has FULL-TEXT search, but it has 50% threshold. It can be removed, but will be slower.

       

      Verity Engine

      pros:

      1. very good for keyword search.

       

      cons:

      1. I have to store data at both verity engine and mySQL