base

  # Returns 'CPANDB'
  my $namespace = CPANDB::Ticket->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 'ticket'
  print CPANDB::Ticket->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.

load

  my $object = CPANDB::Ticket->load( $id );

If your table has single column primary key, a "load" method will be generated in the class. If there is no primary key, the method is not created.

The "load" method provides a shortcut mechanism for fetching a single object based on the value of the primary key. However it should only be used for cases where your code trusts the record to already exists.

It returns a "CPANDB::Ticket" object, or throws an exception if the object does not exist.

select

  # Get all objects in list context
  my @list = CPANDB::Ticket->select;
  
  # Get a subset of objects in scalar context
  my $array_ref = CPANDB::Ticket->select(
      'where id > ? order by id',
      1000,
  );

The "select" method executes a typical SQL "SELECT" query on the ticket table.

It takes an optional argument of a SQL phrase to be added after the "FROM ticket" 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 CPANDB::Ticket objects when called in list context, or a reference to an "ARRAY" of CPANDB::Ticket objects when called in scalar context.

Throws an exception on error, typically directly from the DBI layer.

iterate

  CPANDB::Ticket->iterate( sub {
      print $_->id . "\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 ( CPANDB::Ticket->select ) {
      print $_->id . "\n";
  }

You can filter the list via SQL in the same way you can with "select".

  CPANDB::Ticket->iterate(
      'order by ?', 'id',
      sub {
          print $_->id . "\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.

  CPANDB->iterate(
      'select name from ticket order by id',
      sub {
          print $_->[0] . "\n";
      }
  );

count

  # How many objects are in the table
  my $rows = CPANDB::Ticket->count;
  
  # How many objects 
  my $small = CPANDB::Ticket->count(
      'where id > ?',
      1000,
  );

The "count" method executes a "SELECT COUNT(*)" query on the ticket table.

It takes an optional argument of a SQL phrase to be added after the "FROM ticket" 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.

id

  if ( $object->id ) {
      print "Object has been inserted\n";
  } else {
      print "Object has not been inserted\n";
  }

Returns true, or throws an exception on error.

REMAINING ACCESSORS TO BE COMPLETED