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