NAME
ORDB::CPANRelease::Release - ORDB::CPANRelease class for the release table
DESCRIPTION
TO BE COMPLETED
METHODS
base
# Returns 'ORDB::CPANRelease'
my $namespace = ORDB::CPANRelease::Release->base;
Normally you will only need to work directly with a table class, and only with one ORLite package.
However, if for some reason you need to work with multiple ORLite packages at the same time without hardcoding the root namespace all the time, you can determine the root namespace from an object or table class with the base
method.
table
# Returns 'release'
print ORDB::CPANRelease::Release->table;
While you should not need the name of table for any simple operations, from time to time you may need it programatically. If you do need it, you can use the table
method to get the table name.
select
# Get all objects in list context
my @list = ORDB::CPANRelease::Release->select;
# Get a subset of objects in scalar context
my $array_ref = ORDB::CPANRelease::Release->select(
'where > ? order by ',
1000,
);
The select
method executes a typical SQL SELECT
query on the release table.
It takes an optional argument of a SQL phrase to be added after the FROM release
section of the query, followed by variables to be bound to the placeholders in the SQL phrase. Any SQL that is compatible with SQLite can be used in the parameter.
Returns a list of ORDB::CPANRelease::Release objects when called in list context, or a reference to an ARRAY
of ORDB::CPANRelease::Release objects when called in scalar context.
Throws an exception on error, typically directly from the DBI layer.
iterate
ORDB::CPANRelease::Release->iterate( sub {
print $_-> . "\n";
} );
The iterate
method enables the processing of large tables one record at a time without loading having to them all into memory in advance.
This plays well to the strength of SQLite, allowing it to do the work of loading arbitrarily large stream of records from disk while retaining the full power of Perl when processing the records.
The last argument to iterate
must be a subroutine reference that will be called for each element in the list, with the object provided in the topic variable $_
.
This makes the iterate
code fragment above functionally equivalent to the following, except with an O(1) memory cost instead of O(n).
foreach ( ORDB::CPANRelease::Release->select ) {
print $_-> . "\n";
}
You can filter the list via SQL in the same way you can with select
.
ORDB::CPANRelease::Release->iterate(
'order by ?', '',
sub {
print $_-> . "\n";
}
);
You can also use it in raw form from the root namespace for better control. Using this form also allows for the use of arbitrarily complex queries, including joins. Instead of being objects, rows are provided as ARRAY
references when used in this form.
ORDB::CPANRelease->iterate(
'select name from release order by ',
sub {
print $_->[0] . "\n";
}
);
count
# How many objects are in the table
my $rows = ORDB::CPANRelease::Release->count;
# How many objects
my $small = ORDB::CPANRelease::Release->count(
'where > ?',
1000,
);
The count
method executes a SELECT COUNT(*)
query on the release table.
It takes an optional argument of a SQL phrase to be added after the FROM release
section of the query, followed by variables to be bound to the placeholders in the SQL phrase. Any SQL that is compatible with SQLite can be used in the parameter.
Returns the number of objects that match the condition.
Throws an exception on error, typically directly from the DBI layer.
ACCESSORS
REMAINING ACCESSORS TO BE COMPLETED
SQL
The release table was originally created with the following SQL command.
CREATE TABLE release (
dist text not null,
version text not null,
pass integer not null,
fail integer not null,
na integer not null,
unknown integer not null
)
SUPPORT
ORDB::CPANRelease::Release is part of the ORDB::CPANRelease API.
See the documentation for ORDB::CPANRelease for more information.
AUTHOR
Adam Kennedy <adamk@cpan.org>
COPYRIGHT
Copyright 2011 Adam Kennedy.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
The full text of the license can be found in the LICENSE file included with this module.