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
41
42
43
44
45
46
|
Source: libdancer2-plugin-database-perl
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Uploaders: gregor herrmann <gregoa@debian.org>
Section: perl
Testsuite: autopkgtest-pkg-perl
Priority: optional
Build-Depends: debhelper-compat (= 13)
Build-Depends-Indep: libdancer-plugin-database-core-perl,
libdancer2-perl,
libdbd-sqlite3-perl,
libhttp-message-perl,
libplack-perl,
libtest-pod-perl,
perl
Standards-Version: 4.6.2
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libdancer2-plugin-database-perl
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libdancer2-plugin-database-perl.git
Homepage: https://metacpan.org/release/Dancer2-Plugin-Database
Rules-Requires-Root: no
Package: libdancer2-plugin-database-perl
Architecture: all
Depends: ${misc:Depends},
${perl:Depends},
libdancer-plugin-database-core-perl,
libdancer2-perl
Description: module for easy database connections for Dancer2 applications
Dancer2::Plugin::Database Provides an easy way to obtain a connected DBI
database handle by simply calling the database keyword within your Dancer2
application
.
The module returns a Dancer::Plugin::Database::Core::Handle object, which is
a subclass of DBI's `DBI::db' connection handle object, so it does everything
you'd expect to do with DBI, but also adds a few convenience methods.
.
It takes care of ensuring that the database handle is still connected and
valid. If the handle was last asked for more than
`connection_check_threshold' seconds ago, it will check that the connection
is still alive, using either the `$dbh->ping' method if the DBD driver
supports it, or performing a simple no-op query against the database if not.
If the connection has gone away, a new connection will be obtained and
returned. This avoids any problems for a long-running script where the
connection to the database might go away.
.
Care is taken that handles are not shared across processes/threads, so this
should be thread-safe with no issues with transactions etc.
|
