libpgobject-perl 2.4.0-1 source package in Ubuntu
Changelog
libpgobject-perl (2.4.0-1) unstable; urgency=medium * Team upload. * Import upstream version 2.4.0. * Update years of packaging copyright. * Declare compliance with Debian Policy 4.6.2. * Update debian/upstream/metadata. -- gregor herrmann <email address hidden> Fri, 24 Nov 2023 01:48:44 +0100
Upload details
- Uploaded by:
- Debian Perl Group
- Uploaded to:
- Sid
- Original maintainer:
- Debian Perl Group
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section | |
|---|---|---|---|---|
| Oracular | release | universe | misc | |
| Noble | release | universe | misc |
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| libpgobject-perl_2.4.0-1.dsc | 2.5 KiB | 4e2ea52eb01b6fc92535da96e794e336117987f2d237b70e1882acffb757d1ff |
| libpgobject-perl_2.4.0.orig.tar.gz | 22.8 KiB | cebaa53ee8dde930cd94596bc1f3ac791d6ce04b43f73213aff18e3a23b5f6bf |
| libpgobject-perl_2.4.0-1.debian.tar.xz | 3.3 KiB | 216c4c1cd9d2ee88871c9dc49388b2febf6678ee1c896078c28bc715036a0d4b |
Available diffs
- diff from 2.3.2-1 to 2.4.0-1 (5.8 KiB)
No changes file available.
Binary packages built by this source
- libpgobject-perl: base class for PG Object subclasses
PGObject contains the base routines for object management using discoverable
stored procedures in PostgreSQL databases. PGObject contains only common
functionality and support structures, and low-level API's. Most developers
will want to use more functional modules which add to these functions.
.
The overall approach here is to provide the basics for a toolkit that other
modules can extend. This is thus intended to be a component for building
integration between PostgreSQL user defined functions and Perl objects.
.
Because decisions such as state handling are largely outside of the scope of
this module, this module itself does not do any significant state handling.
Database handles (using DBD::Pg 2.0 or later) must be passed in on every
call. This decision was made in order to allow for diversity in this area,
with the idea that wrapper classes would be written to implement this.
