Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

wiki::toolkit::search::base(3pm) [debian man page]

Wiki::Toolkit::Search::Base(3pm)			User Contributed Perl Documentation			  Wiki::Toolkit::Search::Base(3pm)

NAME
Wiki::Toolkit::Search::Base - Base class for Wiki::Toolkit search plugins. SYNOPSIS
my $search = Wiki::Toolkit::Search::XXX->new( @args ); my %wombat_nodes = $search->search_nodes("wombat"); This class details the methods that need to be overridden by search plugins. METHODS
"new" my $search = Wiki::Toolkit::Search::XXX->new( @args ); Creates a new searcher. By default the arguments are just passed to "_init", so you may wish to override that instead. "search_nodes" # Find all the nodes which contain the word 'expert'. my %results = $search->search_nodes('expert'); Returns a (possibly empty) hash whose keys are the node names and whose values are the scores in some kind of relevance-scoring system I haven't entirely come up with yet. For OR searches, this could initially be the number of terms that appear in the node, perhaps. Defaults to AND searches (if $and_or is not supplied, or is anything other than "OR" or "or"). Searches are case-insensitive. "analyze" @terms = $self->analyze($string) Splits a string into a set of terms for indexing and searching. Typically this is done case-insensitively, splitting at word boundaries, and extracting words that contain at least 1 word characters. "fuzzy_title_match" $wiki->write_node( "King's Cross St Pancras", "A station." ); my %matches = $search->fuzzy_title_match( "Kings Cross St. Pancras" ); Returns a (possibly empty) hash whose keys are the node names and whose values are the scores in some kind of relevance-scoring system I haven't entirely come up with yet. Note that even if an exact match is found, any other similar enough matches will also be returned. However, any exact match is guaranteed to have the highest relevance score. The matching is done against "canonicalised" forms of the search string and the node titles in the database: stripping vowels, repeated letters and non-word characters, and lowercasing. "index_node" $search->index_node($node, $content); Indexes or reindexes the given node in the search engine indexes. You must supply both the node name and its content. canonicalise_title $fuzzy = $self->canonicalise_title( $ node); Returns the node title as suitable for fuzzy searching: with punctuation and spaces removes, vowels removed, and double letters squashed. "delete_node" $search->delete_node($node); Removes the given node from the search indexes. NOTE: It's up to you to make sure the node is removed from the backend store. Croaks on error. "supports_phrase_searches" if ( $search->supports_phrase_searches ) { return $search->search_nodes( '"fox in socks"' ); } Returns true if this search backend supports phrase searching, and false otherwise. "supports_fuzzy_searches" if ( $search->supports_fuzzy_searches ) { return $search->fuzzy_title_match("Kings Cross St Pancreas"); } Returns true if this search backend supports fuzzy title matching, and false otherwise. SEE ALSO
Wiki::Toolkit perl v5.14.2 2012-05-28 Wiki::Toolkit::Search::Base(3pm)

Check Out this Related Man Page

Wiki::Toolkit::Setup::SQLite(3pm)			User Contributed Perl Documentation			 Wiki::Toolkit::Setup::SQLite(3pm)

NAME
Wiki::Toolkit::Setup::SQLite - Set up tables for a Wiki::Toolkit store in a SQLite database. SYNOPSIS
use Wiki::Toolkit::Setup::SQLite; Wiki::Toolkit::Setup::SQLite::setup( $dbfile ); DESCRIPTION
Set up a SQLite database for use as a Wiki::Toolkit store. FUNCTIONS
setup use Wiki::Toolkit::Setup::SQLite; Wiki::Toolkit::Setup::SQLite::setup( $filename ); or Wiki::Toolkit::Setup::SQLite::setup( $dbh ); Takes one argument - either the name of the file that the SQLite database is stored in or an active database handle. NOTE: If a table that the module wants to create already exists, "setup" will leave it alone. This means that you can safely run this on an existing Wiki::Toolkit database to bring the schema up to date with the current Wiki::Toolkit version. If you wish to completely start again with a fresh database, run "cleardb" first. An optional second argument may be passed specifying the schema version to use; this is ONLY intended to be used during unit testing and should not normally be specified. cleardb use Wiki::Toolkit::Setup::SQLite; # Clear out all Wiki::Toolkit tables from the database. Wiki::Toolkit::Setup::SQLite::cleardb( $filename ); or Wiki::Toolkit::Setup::SQLite::cleardb( $dbh ); Takes one argument - either the name of the file that the SQLite database is stored in or an active database handle. Clears out all Wiki::Toolkit store tables from the database. NOTE that this will lose all your data; you probably only want to use this for testing purposes or if you really screwed up somewhere. Note also that it doesn't touch any Wiki::Toolkit search backend tables; if you have any of those in the same or a different database see Wiki::Toolkit::Setup::DBIxFTS or Wiki::Toolkit::Setup::SII, depending on which search backend you're using. ALTERNATIVE CALLING SYNTAX
As requested by Podmaster. Instead of passing arguments to the methods as ($filename) you can pass them as ( { dbname => $filename } ) or indeed ( { dbh => $dbh } ) Note that's a hashref, not a hash. AUTHOR
Kake Pugh (kake@earth.li). COPYRIGHT
Copyright (C) 2002-2004 Kake Pugh. All Rights Reserved. Copyright (C) 2006-2009 the Wiki::Toolkit team. All Rights Reserved. This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. SEE ALSO
Wiki::Toolkit, Wiki::Toolkit::Setup::DBIxFTS, Wiki::Toolkit::Setup::SII perl v5.14.2 2011-09-25 Wiki::Toolkit::Setup::SQLite(3pm)
Man Page