1DBIx::Class::Manual::GlUossesrarCyo(n3t)ributed Perl DocDuBmIexn:t:aCtliaosns::Manual::Glossary(3)
2
3
4
6 DBIx::Class::Manual::Glossary - Clarification of terms used.
7
9 This document lists various terms used in DBIx::Class and attempts to
10 explain them.
11
13 DB schema
14 Refers to a single physical schema within an RDBMS. Synonymous with the
15 terms 'database', for MySQL; and 'schema', for most other RDBMS(s).
16
17 In other words, it's the 'xyz' _thing_ you're connecting to when using
18 any of the following DSN(s):
19
20 dbi:DriverName:xyz@hostname:port
21 dbi:DriverName:database=xyz;host=hostname;port=port
22
23 Inflation
24 The act of turning database row data into objects in language-space.
25 DBIx::Class further allows you to inflate your data into perl objects
26 which more usefully represent their contents. For example:
27 DBIx::Class::InflateColumn::DateTime for datetime or timestamp column
28 data.
29
30 Join
31 This is an SQL keyword that gets mentioned a lot. It is used to fetch
32 data from more than one table at once, by "join"ing the tables on
33 fields where they have common data.
34
35 Normalisation
36 A normalised database is a sane database. Each table contains only data
37 belonging to one concept, related tables refer to the key field or
38 fields of each other. Some links to webpages about normalisation can be
39 found in DBIx::Class::Manual::FAQ.
40
41 ORM
42 Object-relational mapping, or Object-relationship modelling. Either way
43 it's a method of mapping the contents of database tables (rows), to
44 objects in programming-language-space. DBIx::Class is an ORM.
45
46 Relationship
47 In DBIx::Class a relationship defines the connection between exactly
48 two tables. The relationship condition lists the columns in each table
49 that contain the same values. It is used to output an SQL JOIN
50 condition between the tables.
51
52 Relationship bridge
53 A relationship bridge, such as "many_to_many" defines an accessor to
54 retrieve row contents across multiple relationships.
55
56 ResultSet
57 This is an object representing a set of data. It can either be an
58 entire table, or the results of a query. The actual data is not held in
59 the ResultSet, it is only a description of how to fetch the data.
60
61 See also: "METHODS" in DBIx::Class::ResultSet
62
63 ResultSource
64 ResultSource objects represent the source of your data, they are also
65 known as a table objects.
66
67 See also: "METHODS" in DBIx::Class::ResultSource
68
69 Record
70 See Row.
71
72 Row
73 Row objects contain your actual data. They are returned from ResultSet
74 objects.
75
76 Object
77 See Row.
78
79 Schema
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.
84
85
86
87perl v5.12.0 2010-05-12 DBIx::Class::Manual::Glossary(3)