libdbix-class-perl 0.082820-1 source package in Ubuntu
Changelog
libdbix-class-perl (0.082820-1) unstable; urgency=medium
* Import upstream version 0.082820
* debian/copyright: update upstream copyright years and holders,
and packaging copyright years.
* Bump versioned (build) dependency on libmoo-perl.
* Remove all patches. They were cherry-picked from and by upstream.
* Mark package as autopkgtest-able.
* Bump debhelper compatibility level to 9.
-- gregor herrmann <email address hidden> Wed, 12 Aug 2015 20:35:37 +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 | Published | Component | Section |
|---|
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| libdbix-class-perl_0.082820-1.dsc | 3.5 KiB | 4624d924474bc64a3c8e89069b19efa8d7e3314e4fa9df551b3314d32e3ed936 |
| libdbix-class-perl_0.082820.orig.tar.gz | 830.6 KiB | 7b6083a1273d474d785aa93581dc1da334bbe5d83c741574ee2e3942559daeb9 |
| libdbix-class-perl_0.082820-1.debian.tar.xz | 12.7 KiB | 27c81f02365b469d4c58dd420bf078d8702b2ddf81d3626bbbd7e22661235024 |
Available diffs
- diff from 0.082810-2 to 0.082820-1 (40.8 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).
