InstantSpot Search is complete
ColdFusion
I have finally completed the work on the search engine for InstantSpot. We are making use of the full text search capabilities of MySQL to search for matches in both InstantSpot user's pages and blog entries and displaying them 10 records at a time, which seems to be working pretty well. If you see any abnormailites, I would really appreciate you letting me/us know about it.
Seth Bienek said:
Did you consider using ColdFusion's built-in search engine functionality?
This has worked well for me and the performance seems much faster than the hand-rolled approaches I've tried.
This has worked well for me and the performance seems much faster than the hand-rolled approaches I've tried.
Dave Shuck said:
I was really surprised at how quickly we were able to implement it. I can't see much reason to use Verity over it for most searches of database content. MachII made pagination of the results a real pleasure to write as well. Hooray for filters, plugins and listeners! :)
Dave Shuck said:
Sorry, I only half answered the question.
We certainly did consider it. However, we decided not to tie ourselves down to features of a particular product at this point. As of this time, the codebase is portable to BlueDragon, Coldfusion, or even Railo.
Additionally, I went to Ray Camden's Verity talk at CFUnited this year and there was some talk about degradation in performance after X records. I would have to pull out my notes, but after comparing what I learned against the built-in capabilites of MySQL, the database seemed like the logical choice.
We certainly did consider it. However, we decided not to tie ourselves down to features of a particular product at this point. As of this time, the codebase is portable to BlueDragon, Coldfusion, or even Railo.
Additionally, I went to Ray Camden's Verity talk at CFUnited this year and there was some talk about degradation in performance after X records. I would have to pull out my notes, but after comparing what I learned against the built-in capabilites of MySQL, the database seemed like the logical choice.
Loading....