Hey smart monks!

I'm sitting here and thinking about what way to go about indexing text files for fast searching. MySQL apparently has full text search abilities, but then I have to add the whole text into the database. Feels like a waste (even if it may compress the data in the table). With KinoSearch it seems that it creates 2 binary files. I was thinking using KinoSearch to create these files, and then insert them into some table, instead of inserting the text itself. Then just extract this BLOB and use that with KinoSearch. KinoSearch feels faster this way too! Ideas on this?

The thing is. I want it to be easy (and fast) to update this index I have (KindoSearch index). But I'm not sure how good KinoSearch is when it comes to update the index. That is, remove a particular file's index from the big KinoSearch index file. I want speed here! :) And the text-files (and thus the index) may be updated often. How good is it with small changes in a text file? Needs to rebuild the whole thing anyway?

Also, I'm not sure if SQLite even has support for fulltext searching... So, KinoSearch is a good middleman here I think... :)

Update: Forgot to mention that the we are talking about many Mb here. For text files all together. Index smaller ofcource, but can be some 100 Mbs surely... :)

What do you guys think?
/ Ace

In reply to Full Text Searching! by Ace128

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.