CPANDB

 view release on metacpan or  search on metacpan

lib/CPANDB/Author.pod  view on Meta::CPAN

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 C<iterate> must be a subroutine reference that will be
called for each element in the list, with the object provided in the topic
variable C<$_>.

This makes the C<iterate> code fragment above functionally equivalent to the
following, except with an O(1) memory cost instead of O(n).

  foreach ( CPANDB::Author->select ) {
      print $_->author . "\n";
  }

You can filter the list via SQL in the same way you can with C<select>.

  CPANDB::Author->iterate(
      'order by ?', 'author',

lib/CPANDB/Dependency.pod  view on Meta::CPAN

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 C<iterate> must be a subroutine reference that will be
called for each element in the list, with the object provided in the topic
variable C<$_>.

This makes the C<iterate> code fragment above functionally equivalent to the
following, except with an O(1) memory cost instead of O(n).

  foreach ( CPANDB::Dependency->select ) {
      print $_->distribution . "\n";
  }

You can filter the list via SQL in the same way you can with C<select>.

  CPANDB::Dependency->iterate(
      'order by ?', 'distribution',

lib/CPANDB/Distribution.pod  view on Meta::CPAN

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 C<iterate> must be a subroutine reference that will be
called for each element in the list, with the object provided in the topic
variable C<$_>.

This makes the C<iterate> code fragment above functionally equivalent to the
following, except with an O(1) memory cost instead of O(n).

  foreach ( CPANDB::Distribution->select ) {
      print $_->distribution . "\n";
  }

You can filter the list via SQL in the same way you can with C<select>.

  CPANDB::Distribution->iterate(
      'order by ?', 'distribution',

lib/CPANDB/Module.pod  view on Meta::CPAN

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 C<iterate> must be a subroutine reference that will be
called for each element in the list, with the object provided in the topic
variable C<$_>.

This makes the C<iterate> code fragment above functionally equivalent to the
following, except with an O(1) memory cost instead of O(n).

  foreach ( CPANDB::Module->select ) {
      print $_->module . "\n";
  }

You can filter the list via SQL in the same way you can with C<select>.

  CPANDB::Module->iterate(
      'order by ?', 'module',

lib/CPANDB/Requires.pod  view on Meta::CPAN

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 C<iterate> must be a subroutine reference that will be
called for each element in the list, with the object provided in the topic
variable C<$_>.

This makes the C<iterate> code fragment above functionally equivalent to the
following, except with an O(1) memory cost instead of O(n).

  foreach ( CPANDB::Requires->select ) {
      print $_->distribution . "\n";
  }

You can filter the list via SQL in the same way you can with C<select>.

  CPANDB::Requires->iterate(
      'order by ?', 'distribution',

lib/CPANDB/Ticket.pod  view on Meta::CPAN

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 C<iterate> must be a subroutine reference that will be
called for each element in the list, with the object provided in the topic
variable C<$_>.

This makes the C<iterate> code fragment above functionally equivalent to the
following, except with an O(1) memory cost instead of O(n).

  foreach ( CPANDB::Ticket->select ) {
      print $_->id . "\n";
  }

You can filter the list via SQL in the same way you can with C<select>.

  CPANDB::Ticket->iterate(
      'order by ?', 'id',