| 12
 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
 41
 42
 43
 44
 45
 46
 47
 
 | Source: libdbd-sqlite3-perl
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Uploaders: Niko Tyni <ntyni@debian.org>,
           gregor herrmann <gregoa@debian.org>,
           Ansgar Burchardt <ansgar@debian.org>,
           Salvatore Bonaccorso <carnil@debian.org>,
           Xavier Guimard <yadd@debian.org>
Section: perl
Testsuite: autopkgtest-pkg-perl
Priority: optional
Build-Depends: debhelper-compat (= 13),
               dh-sequence-perl-dbi,
               libdbi-perl <!nocheck>,
               libsqlite3-dev (>= 3.46.1~),
               perl-xs-dev,
               perl:native
Standards-Version: 4.7.0
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libdbd-sqlite3-perl
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libdbd-sqlite3-perl.git
Homepage: https://metacpan.org/release/DBD-SQLite
Rules-Requires-Root: no
Package: libdbd-sqlite3-perl
Architecture: any
Multi-Arch: same
Depends: ${misc:Depends},
         ${perl:Depends},
         ${shlibs:Depends}
Description: Perl DBI driver with a self-contained RDBMS
 DBD::SQLite is a Perl DBI driver with a self-contained relational database
 management system. It embeds a small and fast embedded SQL database engine
 called SQLite (see sqlite3) into a DBI driver. It is useful if you want a
 relational database for your project, but don't want to install a large
 RDBMS system like MySQL or PostgreSQL.
 .
 SQLite supports the following features:
 .
  * Implements a large subset of SQL92 (<URL:http://www.sqlite.org/lang.html>)
  * A complete DB in a single disk file
    Everything for your database is stored in a single disk file, making it
    easier to move things around than with DBD::CSV.
  * Atomic commit and rollback
 .
 The engine is very fast, but for updates/inserts/dml it does perform a global
 lock on the entire database. This, obviously, might not be good for multiple
 user systems. The database also appears to be significantly faster if your
 transactions are coarse.
 |