Hello Matt,

Thursday, August 12, 2004, 12:02:04 AM, you wrote:

MS> On Wed, 11 Aug 2004, Pavel wrote:

>> Hello sqlite-users,
>> 
>>   Fri, 16 Jan 2004 Steve O'Hara wrote:
>> 
>> > I was developing my FT engine to run from a CD so I wasn't interested in
>> > keeping my inverted index up to date after deletions/updates to the main
>> > table.  When you add this in too, the heap of code neccersary to implement
>> > this within SQLite gets even longer and more complicated.
>> 
>> I need build a CDROM with full text search function. Can you provide some hints
>> how I can accomplish it?
>> 
>> After reading of mailing list I found out I cannt do this solely with
>> SQLite, so I need some kind of wrapper (preferably in Perl, but it can
>> be another solution).
>> 
>> May be somebody knows a open source or freeware solution?

MS> There are some modules on CPAN which provide generic full text search
MS> backed on any RDBMS. Try http://search.cpan.org/

CPAN was my first search, only was I found was DBIx::FullTextSearch
that require MySQL and DBIx::TextIndex that search in BLOB column (and
not in index).

Or I am missing something (most likely)?

anyway thanks.

P.S. I found something:
http://elucidsoft.net/projects/jsfind/
"jsFind is a powerful set of tools and scripts for adding a search
engine to a CDROM archive or catalog without requiring the user to install anything."

P.P.S. search engine on search.cpan.org dont undestand syntax like
"full text search" (quoted) and return 10234 results to me :-))


--------------------------------------------------------------------------


BTW the "full text search" definition (now I know what it is):

A linguistic search can operate on words and phrases unlike predicate
"LIKE", which works only on character patterns.

A full-text search query returns the results in ranked order, which is
not possible with predicate "LIKE", because it only returns those
results, which contain the query term.

Full-text search can remove noise words from the search criteria,
hence making the search more effective, which is not possible with
predicate "LIKE".

Full-text search is extremely efficient at searching large tables
(greater than 1 million rows) because it uses a pre-composed index. In
comparison to it, predicate "LIKE" searches the entire table for the
required string at the time of query.
        
Full-text search permits language specific search , which is not
possible with predicate "LIKE ".

( copy/paste from: http://www.daffodildb.com/full-text-search.php )


-- 
Best regards,
 Pavel                            mailto:[EMAIL PROTECTED]

Reply via email to