DBIx::Class::Manual::Glossary - Clarification of terms used.


DBIx::Class::Manual::Glossary - Clarification of terms used.


This document lists various terms used in DBIx::Class and attempts to explain them.



The act of turning database row data into objects in language-space. DBIx::Class further allows you to inflate your data into perl objects which more usefully represent their contents. For example: the DBIx::Class::InflateColumn::DateTime manpage for datetime or timestamp column data.


This is an SQL keyword that gets mentioned a lot. It is used to fetch data from more than one table at once, by joining the tables on fields where they have common data.


A normalised database is a sane database. Each table contains only data belonging to one concept, related tables refer to the key field or fields of each other. Some links to webpages about normalisation can be found in DBIx::Class::Manual::FAQ.


Object-relational mapping, or Object-relationship modelling. Either way it's a method of mapping the contents of database tables (rows), to objects in programming-language-space. DBIx::Class is an ORM.


This is an object representing a set of data. It can either be an entire table, or the results of a query. The actual data is not held in the ResultSet, it is only a description of how to fetch the data.

See also: METHODS in the DBIx::Class::ResultSet manpage


ResultSource objects represent the source of your data, they are also known as a table objects.

See also: METHODS in the DBIx::Class::ResultSource manpage


See Row.


Row objects contain your actual data. They are returned from ResultSet objects.


See Row.


A Schema object represents your entire table collection, plus the connection to the database. You can create one or more schema objects, connected to various databases, with various users, using the same set of table (ResultSource) definitions.

 DBIx::Class::Manual::Glossary - Clarification of terms used.