Commit | Line | Data |
24105556 |
1 | =head1 NAME |
2 | |
880a1a0c |
3 | DBIx::Class::Manual::Glossary - Clarification of terms used. |
24105556 |
4 | |
5 | =head1 INTRODUCTION |
6 | |
7 | This document lists various terms used in DBIx::Class and attempts to explain them. |
8 | |
9 | =head1 TERMS |
10 | |
11 | =head2 ORM |
12 | |
13 | =head2 ResultSet |
14 | |
15 | This is an object representing a set of data. It can either be an |
16 | entire table, or the results of a query. The actual data is not held |
17 | in the ResultSet, it is only a description of how to fetch the data. |
18 | |
19 | See also: L<DBIx::Class::ResultSet/METHODS> |
20 | |
21 | =head2 ResultSource |
22 | |
23 | ResultSource objects represent the source of your data, they are also known as |
24 | a table objects. |
25 | |
26 | See also: L<DBIx::Class::ResultSource/METHODS> |
27 | |
28 | =head2 Record |
29 | |
30 | See Row. |
31 | |
32 | =head2 Row |
33 | |
34 | Row objects contain your actual data. They are returned from ResultSet objects. |
35 | |
36 | =head2 Object |
37 | |
38 | See Row. |
39 | |
40 | =head2 Schema |
41 | |
42 | A Schema object represents your entire table collection, plus the |
43 | connection to the database. You can create one or more schema objects, |
44 | connected to various databases, with various users, using the same set |
45 | of table (ResultSource) definitions. |