Ok, first another quick question. If I could order the results by the number of times the pattern was matched, it would be just what I was looking for. Something like this:

SELECT * FROM foo WHERE Description LIKE '%$word%' ORDER BY "number of matches?" LIMIT $start, $stop

Ill eventually use placeholders before this goes live, I read the link you gave me and it is indeed a good idea to use them :P

I also read the search engine article and I must say, making it like that would be a LOT of work for such a small, little used project. It looks fun to make though. Ill only go that road if I have to. Since this search wouldnt be used much, a cheap, simple, and slower solution will do. As long as it isnt toooo slow.

What do you guys think?

In reply to Re: Inefficient search algorithm? by ruhk
in thread Inefficient search algorithm? by ruhk

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.