DBIX::Class::Recordset - Responsible for fetching and creating recordsets.
The recordset is also know as an iterator.
The recordset constructor. Takes a db class and an attribute hash (see below for more info on attributes)
Return a storage driven cursor to the given record set.
return a number of elements from the given record set.
Returns the next element in this record set.
Performs an SQL count with the same query as the resultset was built with to find the number of elements.
Returns all elements in the recordset. Is called implictly if the search method is used in list context.
Reset this recordset's cursor, so you can iterate through the elements again.
resets the recordset and returns the first element.
Deletes all elements in the recordset.
Returns a Data::Page object for the current resultset. Only makes sense for queries with page turned on.
Returns a new recordset representing a given page.
The recordset is responsible for handling the various attributes that can be passed in with the search functions. Here's an overview of them:
Which column to order the results by.
Which cols should be retrieved on the first search.
Contains a list of relations that should be joined for this query. Can also contain a hash referece to refer to that relation's relations.
This attribute can contain a arrayref of elements. each element can be another arrayref, to nest joins, or it can be a hash which represents the two sides of the join.
*NOTE* Use this on your own risk. This allows you to shoot your foot off!
Should the resultset be paged? This can also be enabled by using the 'page' option.
For paged resultsset, how many rows per page
For paged resultsset, which page to start on.