| 1 |
Source: libdbix-fulltextsearch-perl |
| 2 |
Section: perl |
| 3 |
Priority: optional |
| 4 |
Build-Depends: debhelper (>= 10) |
| 5 |
Build-Depends-Indep: perl (>= 5.8.0-7), libdbd-mysql-perl |
| 6 |
Maintainer: Debian Perl Group <[email protected]> |
| 7 |
Uploaders: Dominic Hargreaves <[email protected]> |
| 8 |
Standards-Version: 4.1.3 |
| 9 |
Homepage: https://metacpan.org/release/DBIx-FullTextSearch |
| 10 |
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libdbix-fulltextsearch-perl.git |
| 11 |
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libdbix-fulltextsearch-perl |
| 12 |
|
| 13 |
Package: libdbix-fulltextsearch-perl |
| 14 |
Architecture: all |
| 15 |
Depends: ${perl:Depends}, ${misc:Depends}, libparse-recdescent-perl, |
| 16 |
libdbd-mysql-perl, libwww-perl |
| 17 |
Description: Indexing documents with MySQL as storage |
| 18 |
DBIx::FullTextSearch is a flexible solution for indexing contents of documents. |
| 19 |
It uses the MySQL database to store the information about words and |
| 20 |
documents and provides Perl interface for indexing new documents, |
| 21 |
making changes and searching for matches. For DBIx::FullTextSearch, a document |
| 22 |
is nearly anything -- Perl scalar, file, Web document, database field. |
| 23 |
. |
| 24 |
The basic style of interface is shown above. What you need is a MySQL |
| 25 |
database and a DBI with DBD::mysql. Then you create a DBIx::FullTextSearch |
| 26 |
index -- a set of tables that maintain all necessary information. Once created |
| 27 |
it can be accessed many times, either for updating the index (adding |
| 28 |
documents) or searching. |
| 29 |
. |
| 30 |
DBIx::FullTextSearch uses one basic table to store parameters of the index. |
| 31 |
Second table is used to store the actual information about documents and words, |
| 32 |
and depending on the type of the index (specified during index creation) |
| 33 |
there may be more tables to store additional information (like |
| 34 |
conversion from external string names (eg. URL's) to internal numeric |
| 35 |
form). For a user, these internal thingies and internal behaviour of the |
| 36 |
index are not important. The important part is the API, the methods to |
| 37 |
index document and ask questions about words in documents. However, |
| 38 |
certain understanding of how it all works may be useful when you are |
| 39 |
deciding if this module is for you and what type of index will best |
| 40 |
suit your needs. |