3 DBIx::Class::Manual::Glossary - Clarification of terms used.
7 This document lists various terms used in DBIx::Class and attempts to
14 The act of turning database row data into objects in
15 language-space. DBIx::Class further allows you to inflate your data
16 into perl objects which more usefully represent their contents. For
17 example: L<DBIx::Class::InflateColumn::DateTime> for datetime or
18 timestamp column data.
22 This is an SQL keyword that gets mentioned a lot. It is used to fetch
23 data from more than one table at once, by C<join>ing the tables on
24 fields where they have common data.
28 A normalised database is a sane database. Each table contains only
29 data belonging to one concept, related tables refer to the key field
30 or fields of each other. Some links to webpages about normalisation
31 can be found in L<DBIx::Class::Manual::FAQ|the FAQ>.
35 Object-relational mapping, or Object-relationship modelling. Either
36 way it's a method of mapping the contents of database tables (rows),
37 to objects in programming-language-space. DBIx::Class is an ORM.
41 In DBIx::Class a relationship defines the connection between exactly
42 two tables. The relationship condition lists the columns in each table
43 that contain the same values. It is used to output an SQL JOIN
44 condition between the tables.
46 =head2 Relationship bridge
48 A relationship bridge, such as C<many_to_many> defines an accessor to
49 retrieve row contents across multiple relationships.
53 This is an object representing a set of data. It can either be an
54 entire table, or the results of a query. The actual data is not held
55 in the ResultSet, it is only a description of how to fetch the data.
57 See also: L<DBIx::Class::ResultSet/METHODS>
61 ResultSource objects represent the source of your data, they are also known as
64 See also: L<DBIx::Class::ResultSource/METHODS>
72 Row objects contain your actual data. They are returned from ResultSet objects.
80 A Schema object represents your entire table collection, plus the
81 connection to the database. You can create one or more schema objects,
82 connected to various databases, with various users, using the same set
83 of table (ResultSource) definitions.