use Perl

• Perl.com (Score:1)

  by chromatic (983)

  I'm interested in improvements to Perl.com; I'm exploring ways to improve the searching and findability of articles across the entire O'Reilly Network. Please feel free to send me ideas.
  • Re:Perl.com (Score:2)

    by TeeJay (2309)

    see my response on the blog - I couldn't even find my article on searching through perl.com, found it straight away with google.

    It would be nice if perl.com could showcase good perl solutions.

    If I knew what perl.com was using I would be happy to make suggestions.

    --
    
    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;
• Maybe these can help (Score:1)

  by melo (332)

  http://search.cpan.org/~tjmather/DBIx-FullTextSearch-0.73/
  http://search.cpan.o rg/~tmtm/Class-DBI-mysql-FullTextSearch-0.09/
  http://search.cpan.org/~snowhare/ Search-InvertedIndex-1.14/
  
  I used the last one with good results.
  --

  --
  life is short
  • Re:Maybe these can help (Score:2)

    by TeeJay (2309)

    Yup the last one is a reverse index. They work nicely and are trivial to write and customise.

    I wrote a handy class that implements cross-object context specific searching - Class-Indexed-0.01 [cpan.org]

    Its based on the article I wrote for perl.com

    The others aren't a solution - native RDBMS fulltext searching is only useful for really trivial cases - if your data is only in a single table and has a very simple structure so you are only interested in 1 or 2 columns and they don't change - move beyond that and nati

    --
    
    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;
    • Re:Maybe these can help (Score:1)

      by perrin (4270)

      It depends on how the database implements the full text search. Often it is just a reverse index under the covers, with some stemming and phrase support bolted on.

      I agree that a reverse index is typically the way to go for custom searching. It scales well and is very customizable.
      • Re:Maybe these can help (Score:2)

        by TeeJay (2309)

        I have yet to see an RDBMS native fulltext search that is as good as a handwritten one - all are held back by a total lack of customisation or weighting and can only apply to a single table. Very few provide features like stemming although they can provide some simple phrase matching and global weightings (i.e. common words may score less, etc).

        As I said, even a good native RDBMS can be improved on trivially with a competent custom reverse index, as stemming, etc are trivial in perl. Native RDBMS are only

        --
        
        @JAPH = qw(Hacker Perl Another Just);
        print reverse @JAPH;