# PODNAME: DBIO::Manual::Glossary
# ABSTRACT: Clarification of terms used.

__END__

=pod

=encoding UTF-8

=head1 NAME

DBIO::Manual::Glossary - Clarification of terms used.

=head1 VERSION

version 0.900002

=head1 INTRODUCTION

This document lists various terms used in DBIO and attempts to
explain them.

=head1 DBIO TERMS

=head2 DB schema

Refers to a single physical schema within an RDBMS. Synonymous with the terms
'database', for MySQL; and 'schema', for most other RDBMS(s).

In other words, it's the 'xyz' _thing_ you're connecting to when using any of
the following L<DSN|DBI/connect>(s):

  dbi:DriverName:xyz@hostname:port
  dbi:DriverName:database=xyz;host=hostname;port=port

=head2 Inflation

The act of turning database row data into objects in
language-space. DBIO result classes can be set up to inflate
your data into perl objects which more usefully represent their
contents. For example: L<DBIO::InflateColumn::DateTime> for
datetime or timestamp column data.

See also L<DBIO::InflateColumn>.

=head2 Deflation

The opposite of L</Inflation>. Existing perl objects that represent
column values can be passed to DBIO methods to store into the
database. For example a L<DateTime> object can be automatically
deflated into a datetime string for insertion.

See L<DBIO::InflateColumn> and other modules in that namespace.

=head2 ORM

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. DBIO is an ORM.

=head2 Relationship

In DBIO a relationship defines the connection between exactly
two tables. The relationship condition lists the columns in each table
that contain the same values. It is used to output an SQL JOIN
condition between the tables.

=head2 Relationship bridge

A relationship bridge, such as C<many_to_many> defines an accessor to
retrieve row contents across multiple relationships.

The difference between a bridge and a relationship is, that the bridge
cannot be used to C<join> tables in a C<search>, instead its component
relationships must be used.

=head2 Schema

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 L</Result Class> definitions.

At least one L<DBIO::Schema> class is needed per database.

=head2 Result Class

A Result class defines both a source of data (usually one per table),
and the methods that will be available in the L</Result> objects
created using that source.

One Result class is needed per data source (table, view, query) used
in your application, they should inherit from L<DBIO::Core>.

See also: L<DBIO::Manual::ResultClass>

=head2 ResultSource

ResultSource objects represent the source of your data, these are
sometimes (incorrectly) called table objects.

ResultSources do not need to be directly created, a ResultSource
instance is created for each L</Result Class> in your L</Schema>, by
the proxied methods C<table> and C<add_columns>.

See also: L<DBIO::ResultSource/METHODS>

=head2 ResultSet

This is an object representing a set of conditions to filter 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: L<DBIO::ResultSet/METHODS>

=head2 Result

Result objects contain your actual data. They are returned from
ResultSet objects.  These are sometimes (incorrectly) called
row objects, including older versions of the documentation.

See also: L<DBIO::Manual::ResultClass>

=head2 Row

See Result.

=head2 Object

See Result.

=head2 Record

See Result.

=head2 prefetch

Similar to a join, except the related result objects are fetched and
cached for future use, instead of used directly from the ResultSet.  This
allows you to jump to different relationships within a Result without
worrying about generating a ton of extra SELECT statements.

=head1 SQL TERMS

=head2 CRUD

Create, Read, Update, Delete.  A general concept of something that can
do all four operations (INSERT, SELECT, UPDATE, DELETE), usually at a
row-level.

=head2 Join

This is an SQL keyword, it is used to link multiple tables in one SQL
statement. This enables us to fetch data from more than one table at
once, or filter data based on content in another table, without having
to issue multiple SQL queries.

=head2 Normalisation

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 L<the FAQ|DBIO::Manual::FAQ>.

=head2 Related data

In SQL, related data actually refers to data that are normalised into
the same table. (Yes. DBIO does mis-use this term.)

=head1 AUTHOR

DBIO & DBIx::Class Authors

=head1 COPYRIGHT AND LICENSE

Copyright (C) 2026 DBIO Authors
Portions Copyright (C) 2005-2025 DBIx::Class Authors
Based on DBIx::Class, heavily modified.

This is free software; you can redistribute it and/or modify it under
the same terms as the Perl 5 programming language system itself.

=cut
