[Bast-commits] r4272 - in DBIx-Class/0.08/trunk/lib/DBIx/Class: .
Manual
castaway at dev.catalyst.perl.org
castaway at dev.catalyst.perl.org
Wed Apr 16 21:57:22 BST 2008
Author: castaway
Date: 2008-04-16 21:57:22 +0100 (Wed, 16 Apr 2008)
New Revision: 4272
Modified:
DBIx-Class/0.08/trunk/lib/DBIx/Class/Manual/Intro.pod
DBIx-Class/0.08/trunk/lib/DBIx/Class/Relationship.pm
DBIx-Class/0.08/trunk/lib/DBIx/Class/Storage.pm
Log:
Documentation updates from omega, carbon
Modified: DBIx-Class/0.08/trunk/lib/DBIx/Class/Manual/Intro.pod
===================================================================
--- DBIx-Class/0.08/trunk/lib/DBIx/Class/Manual/Intro.pod 2008-04-14 03:58:45 UTC (rev 4271)
+++ DBIx-Class/0.08/trunk/lib/DBIx/Class/Manual/Intro.pod 2008-04-16 20:57:22 UTC (rev 4272)
@@ -13,14 +13,16 @@
Here are a few simple tips that will help you get your bearings with
DBIx::Class.
-=head2 Tables become ResultSources
+=head2 Tables become Result classes
-DBIx::Class needs to know what your Table structure looks like. You do that by
-defining L<DBIx::Class::ResultSource>s. Each table gets a ResultSource, which
-defines the Columns it has, along with any Relationships it has to other tables.
-(And oh, so much more besides) The important thing to understand:
+DBIx::Class needs to know what your Table structure looks like. You
+do that by defining Result classes. Result classes are defined by
+calling methods proxied to L<DBIx::Class::ResultSource>. Each Result
+class defines one Table, which defines the Columns it has, along with
+any Relationships it has to other tables. (And oh, so much more
+besides) The important thing to understand:
- A ResultSource == Table
+ A Result class == Table
(most of the time, but just bear with my simplification)
@@ -62,6 +64,11 @@
Setting up a ResultSet does not execute the query; retrieving
the data does.
+=head2 Search results are returned as Rows
+
+Rows of the search from the database are blessed into
+L<DBIx::Class::Row> objects.
+
=head1 SETTING UP DBIx::Class
Let's look at how you can set and use your first native L<DBIx::Class> tree.
Modified: DBIx-Class/0.08/trunk/lib/DBIx/Class/Relationship.pm
===================================================================
--- DBIx-Class/0.08/trunk/lib/DBIx/Class/Relationship.pm 2008-04-14 03:58:45 UTC (rev 4271)
+++ DBIx-Class/0.08/trunk/lib/DBIx/Class/Relationship.pm 2008-04-16 20:57:22 UTC (rev 4272)
@@ -60,6 +60,7 @@
my $fred = $schema->resultset('Author')->find({ Name => 'Fred' });
my $fredsbooks = $schema->resultset('Book')->search({ Author => $fred->ID });
+
With a has_many relationship called "books" on Author (see below for details),
we can do this instead:
Modified: DBIx-Class/0.08/trunk/lib/DBIx/Class/Storage.pm
===================================================================
--- DBIx-Class/0.08/trunk/lib/DBIx/Class/Storage.pm 2008-04-14 03:58:45 UTC (rev 4271)
+++ DBIx-Class/0.08/trunk/lib/DBIx/Class/Storage.pm 2008-04-16 20:57:22 UTC (rev 4272)
@@ -469,7 +469,8 @@
=head1 SEE ALSO
-L<DBIx::Class::Storage::DBI> - reference storage inplementation using SQL::Abstract and DBI.
+L<DBIx::Class::Storage::DBI> - reference storage implementation using
+SQL::Abstract and DBI.
=head1 AUTHORS
More information about the Bast-commits
mailing list