NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Maybe these can help (Score:1)
http://search.cpan.
http://search.cpan.org/~snowhare
I used the last one with good results.
--
life is short
Re:Maybe these can help (Score:2)
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)
I agree that a reverse index is typically the way to go for custom searching. It scales well and is very customizable.
Reply to This
Parent
Re:Maybe these can help (Score:2)
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;