libdbix-class-perl 0.082820-2 source package in Ubuntu
Changelog
libdbix-class-perl (0.082820-2) unstable; urgency=medium * Rename autopkgtest configuration file(s) as per new pkg-perl- autopkgtest schema. * Add patch from upstream Git repo which fixes the test on newer libsqlite versions, and demotes it to an author test. (Closes: #805233) -- gregor herrmann <email address hidden> Sun, 15 Nov 2015 23:29:28 +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 | Published | Component | Section |
---|
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
libdbix-class-perl_0.082820-2.dsc | 3.5 KiB | 027042777b596f66cd58a9ea918bb1b8a2ecd2236095c6bcac3435d67d044620 |
libdbix-class-perl_0.082820.orig.tar.gz | 830.6 KiB | 7b6083a1273d474d785aa93581dc1da334bbe5d83c741574ee2e3942559daeb9 |
libdbix-class-perl_0.082820-2.debian.tar.xz | 14.4 KiB | cfbb9afda1b62ba85053dab7513f4fe5d7501bfa45dbc0dcc74a446049dd2977 |
Available diffs
- diff from 0.082820-1 to 0.082820-2 (2.4 KiB)
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).