| 1 |
Source: libpgobject-perl |
| 2 |
Maintainer: Debian Perl Group <[email protected]> |
| 3 |
Uploaders: Robert James Clay <[email protected]> |
| 4 |
Section: perl |
| 5 |
Testsuite: autopkgtest-pkg-perl |
| 6 |
Priority: optional |
| 7 |
Build-Depends: debhelper-compat (= 13) |
| 8 |
Build-Depends-Indep: libcarp-clan-perl <!nocheck>, |
| 9 |
libdbd-pg-perl <!nocheck>, |
| 10 |
liblist-moreutils-perl <!nocheck>, |
| 11 |
liblog-any-perl <!nocheck>, |
| 12 |
libscalar-list-utils-perl <!nocheck>, |
| 13 |
libtest-exception-perl <!nocheck>, |
| 14 |
libtest-pod-coverage-perl <!nocheck>, |
| 15 |
libtest-pod-perl <!nocheck>, |
| 16 |
perl |
| 17 |
Standards-Version: 4.6.2 |
| 18 |
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libpgobject-perl |
| 19 |
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libpgobject-perl.git |
| 20 |
Homepage: https://metacpan.org/release/PGObject/ |
| 21 |
Rules-Requires-Root: no |
| 22 |
|
| 23 |
Package: libpgobject-perl |
| 24 |
Architecture: all |
| 25 |
Depends: ${misc:Depends}, |
| 26 |
${perl:Depends}, |
| 27 |
libcarp-clan-perl, |
| 28 |
libdbd-pg-perl, |
| 29 |
liblist-moreutils-perl, |
| 30 |
liblog-any-perl, |
| 31 |
libscalar-list-utils-perl |
| 32 |
Description: base class for PG Object subclasses |
| 33 |
PGObject contains the base routines for object management using discoverable |
| 34 |
stored procedures in PostgreSQL databases. PGObject contains only common |
| 35 |
functionality and support structures, and low-level API's. Most developers |
| 36 |
will want to use more functional modules which add to these functions. |
| 37 |
. |
| 38 |
The overall approach here is to provide the basics for a toolkit that other |
| 39 |
modules can extend. This is thus intended to be a component for building |
| 40 |
integration between PostgreSQL user defined functions and Perl objects. |
| 41 |
. |
| 42 |
Because decisions such as state handling are largely outside of the scope of |
| 43 |
this module, this module itself does not do any significant state handling. |
| 44 |
Database handles (using DBD::Pg 2.0 or later) must be passed in on every |
| 45 |
call. This decision was made in order to allow for diversity in this area, |
| 46 |
with the idea that wrapper classes would be written to implement this. |