libdbix-class-perl 0.082843-1 source package in Ubuntu

Changelog

libdbix-class-perl (0.082843-1) unstable; urgency=medium

  * Import upstream version 0.082843.
  * Update years of upstream copyright.
  * Add new upstream copyright holder.
  * Drop SQLite-3.37.0.patch, applied upstream.
  * Declare compliance with Debian Policy 4.6.1.

 -- gregor herrmann <email address hidden>  Sun, 22 May 2022 00:34:59 +0200

Upload details

Uploaded by:
Debian Perl Group
Uploaded to:
Sid
Original maintainer:
Debian Perl Group
Architectures:
all
Section:
perl
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Oracular release universe perl
Noble release universe perl
Mantic release universe perl
Lunar release universe perl

Builds

Kinetic: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
libdbix-class-perl_0.082843-1.dsc 3.8 KiB 8b97616f09f799a0d61a259ab9686e62ad7ff4e3db87d11c26a4ea83026f2dee
libdbix-class-perl_0.082843.orig.tar.gz 858.8 KiB 341e0b6ecb29d8c49174a6c09d7c6dbf38729ba4015ee7fd70360a4ffee1f251
libdbix-class-perl_0.082843-1.debian.tar.xz 14.1 KiB 92564c8afc12fbbea4f2c1c0457dca2bf1ee6c00cb6a790b61483ddcfacc0ee9

Available diffs

No changes file available.

Binary packages built by this source

libdbix-class-perl: extensible and flexible object <-> relational mapper

 DBIx::Class is an SQL to OO mapper with an object API inspired by Class::DBI
 (and a compatibility layer as a springboard for porting) and a resultset API
 that allows abstract encapsulation of database operations. It aims to make
 representing queries in your code as perl-ish as possible while still
 providing access to as many of the capabilities of the database as possible,
 including retrieving related records from multiple tables in a single query,
 JOIN, LEFT JOIN, COUNT, DISTINCT, GROUP BY and HAVING support.
 .
 DBIx::Class can handle multi-column primary and foreign keys, complex queries
 and database-level paging, and does its best to only query the database in
 order to return something you've directly asked for. If a resultset is used
 as an iterator it only fetches rows off the statement handle as requested
 in order to minimise memory usage. It has auto-increment support for SQLite,
 MySQL, PostgreSQL, Oracle, SQL Server and DB2 and is known to be used in
 production on at least the first four, and is fork- and thread-safe out of
 the box (although your DBD may not be).