Resolve $rsrc instance duality on metadata traversal

[dbsrgits/DBIx-Class.git] / lib / DBIx / Class / Manual / Glossary.pod

diff --git a/lib/DBIx/Class/Manual/Glossary.pod b/lib/DBIx/Class/Manual/Glossary.pod
index 4feb8e1..ae783a5 100644 (file)
--- a/lib/DBIx/Class/Manual/Glossary.pod
+++ b/lib/DBIx/Class/Manual/Glossary.pod
@@ -66,11 +66,11 @@ relationships must be used.
 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.
+of table L</Result Class> definitions.
 
 At least one L<DBIx::Class::Schema> class is needed per database.
 
-=head2 Result class
+=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
@@ -87,7 +87,7 @@ 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
+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<DBIx::Class::ResultSource/METHODS>
@@ -101,14 +101,6 @@ fetch the data.
 
 See also: L<DBIx::Class::ResultSet/METHODS>
 
-=head2 Record
-
-See Result.
-
-=head2 Row
-
-See Result.
-
 =head2 Result
 
 Result objects contain your actual data. They are returned from
@@ -117,17 +109,21 @@ row objects, including older versions of the DBIC documentation.
 
 See also: L<DBIx::Class::Manual::ResultClass>
 
+=head2 Row
+
+See Result.
+
 =head2 Object
 
 See Result.
 
-=head2 join
+=head2 Record
 
-See Join.
+See Result.
 
 =head2 prefetch
 
-Similiar to a join, except the related result objects are fetched and
+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.
@@ -152,17 +148,20 @@ to issue multiple SQL queries.
 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<DBIx::Class::Manual::FAQ|the FAQ>.
+can be found in L<the FAQ|DBIx::Class::Manual::FAQ>.
 
 =head2 Related data
 
 In SQL, related data actually refers to data that are normalised into
 the same table. (Yes. DBIC does mis-use this term.)
 
-=head1 AUTHOR AND CONTRIBUTORS
+=head1 FURTHER QUESTIONS?
 
-See L<AUTHOR|DBIx::Class/AUTHOR> and L<CONTRIBUTORS|DBIx::Class/CONTRIBUTORS> in DBIx::Class
+Check the list of L<additional DBIC resources|DBIx::Class/GETTING HELP/SUPPORT>.
 
-=head1 LICENSE
+=head1 COPYRIGHT AND LICENSE
 
-You may distribute this code under the same terms as Perl itself.
+This module is free software L<copyright|DBIx::Class/COPYRIGHT AND LICENSE>
+by the L<DBIx::Class (DBIC) authors|DBIx::Class/AUTHORS>. You can
+redistribute it and/or modify it under the same terms as the
+L<DBIx::Class library|DBIx::Class/COPYRIGHT AND LICENSE>.