openKylin libdbix-class-perl package

libdbix-class-perl 0.082843-ok1 source package in openKylin

Changelog

libdbix-class-perl (0.082843-ok1) nile; urgency=medium

  * Build for openKylin.

 -- openKylinBot <email address hidden>  Tue, 07 May 2024 09:40:16 +0800

Upload details

Uploaded by:
openKylinBot
Sponsored by:
Cibot
Uploaded to:
Nile V2.0
Original maintainer:
Openkylin Developers
Architectures:
all
Section:
perl
Urgency:
Medium Urgency

Publishing See full publishing history

Series Pocket Published Component Section
Huanghe V3.0 proposed main perl
Huanghe V3.0 release main perl
Nile V2.0 release main perl
Nile V2.0 proposed main perl

Builds

Nile V2.0: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
libdbix-class-perl_0.082843.orig.tar.gz 858.8 KiB 341e0b6ecb29d8c49174a6c09d7c6dbf38729ba4015ee7fd70360a4ffee1f251
libdbix-class-perl_0.082843-ok1.debian.tar.xz 7.4 KiB c781cbb5ba90efabd2cb919565bd1403f214dbb111c576e47a9f3af335c1ba16
libdbix-class-perl_0.082843-ok1.dsc 3.4 KiB dfb94cb17f3e1c6c5f42284a066578b2e2f414bbb044124844a73aea6b184c88

View changes file

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