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

Changelog

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

  [ Salvatore Bonaccorso ]
  * debian/control: Use HTTPS transport protocol for Vcs-Git URI

  [ gregor herrmann ]
  * Import upstream version 0.082821
  * Drop 0001-Adjust-view-dependency-tests-to-work-on-newer-libsql.patch
    which was cherry-picked from upstream Git.
  * Update upstream copyright holders and years.
  * Update years of packaging copyright.
  * Declare compliance with Debian Policy 3.9.7.
  * Add a patch to fix some spelling mistakes.

 -- gregor herrmann <email address hidden>  Sat, 13 Feb 2016 19:56:26 +0100

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
Xenial release universe perl

Builds

Xenial: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
libdbix-class-perl_0.082821-1.dsc 3.5 KiB 34d1326e6461c1123dc4abcf65d9e1224eae5b829cd0952b3d6ff1324be368b9
libdbix-class-perl_0.082821.orig.tar.gz 832.9 KiB dc6e0ce7fa4f732c6e584e89019df9cb8ac25d3f7bd51b94ba4d97cffd8a2cde
libdbix-class-perl_0.082821-1.debian.tar.xz 13.8 KiB 7ec7c9816e0f528fe6926a635a2405b1fc7402fae331b6a0d90a24b6962f37b1

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).