File: control

package info (click to toggle)
libdbix-fulltextsearch-perl 0.73-12
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster, sid
  • size: 500 kB
  • sloc: perl: 1,617; makefile: 7
file content (40 lines) | stat: -rw-r--r-- 2,210 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
Source: libdbix-fulltextsearch-perl
Section: perl
Priority: optional
Build-Depends: debhelper (>= 10)
Build-Depends-Indep: perl (>= 5.8.0-7), libdbd-mysql-perl
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Uploaders: Dominic Hargreaves <dom@earth.li>
Standards-Version: 4.1.3
Homepage: https://metacpan.org/release/DBIx-FullTextSearch
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libdbix-fulltextsearch-perl.git
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libdbix-fulltextsearch-perl

Package: libdbix-fulltextsearch-perl
Architecture: all
Depends: ${perl:Depends}, ${misc:Depends}, libparse-recdescent-perl,
         libdbd-mysql-perl, libwww-perl
Description: Indexing documents with MySQL as storage
 DBIx::FullTextSearch is a flexible solution for indexing contents of documents.
 It uses the MySQL database to store the information about words and
 documents and provides Perl interface for indexing new documents,
 making changes and searching for matches.  For DBIx::FullTextSearch, a document
 is nearly anything -- Perl scalar, file, Web document, database field.
 .
 The basic style of interface is shown above. What you need is a MySQL
 database and a DBI with DBD::mysql. Then you create a DBIx::FullTextSearch
 index  -- a set of tables that maintain all necessary information. Once created
 it can be accessed many times, either for updating the index (adding
 documents) or searching.
 .
 DBIx::FullTextSearch uses one basic table to store parameters of the index.
 Second table is used to store the actual information about documents and words,
 and depending on the type of the index (specified during index creation)
 there may be more tables to store additional information (like
 conversion from external string names (eg. URL's) to internal numeric
 form). For a user, these internal thingies and internal behaviour of the
 index are not important. The important part is the API, the methods to
 index document and ask questions about words in documents. However,
 certain understanding of how it all works may be useful when you are
 deciding if this module is for you and what type of index will best
 suit your needs.