[Catalyst-commits] r12471 - trunk/examples/CatalystAdvent/root/2009
frew at dev.catalyst.perl.org
frew at dev.catalyst.perl.org
Wed Dec 23 16:58:27 GMT 2009
Author: frew
Date: 2009-12-23 16:58:26 +0000 (Wed, 23 Dec 2009)
New Revision: 12471
Modified:
trunk/examples/CatalystAdvent/root/2009/20.pod
Log:
fix capiltalization of pod link
Modified: trunk/examples/CatalystAdvent/root/2009/20.pod
===================================================================
--- trunk/examples/CatalystAdvent/root/2009/20.pod 2009-12-23 15:25:48 UTC (rev 12470)
+++ trunk/examples/CatalystAdvent/root/2009/20.pod 2009-12-23 16:58:26 UTC (rev 12471)
@@ -61,7 +61,7 @@
=head2 SubClass
-L<DBIx::Class::Helper::Subclass> is certainly the most complex of
+L<DBIx::Class::Helper::SubClass> is certainly the most complex of
these components, but I would argue it is the most important as
well. This component allows B<almost> seamless subclassing of
C<DBIx::Class> ResultSources. It does things like C<<
@@ -72,7 +72,7 @@
At work I'd like to define a set of tables for authorization - users,
roles, permissions, and join tables between them. I do not want to
copy and paste this code to our many disparate
-projects. L<DBIx::Class::Helper::SubClass> solves the problem nicely.
+projects. L<DBIx::Class::Helper::SubClass> solves the problem nicely.
Another reason to use this helper is to define a table without certain
columns (TEXT columns come to mind). Instead of redefining the table
More information about the Catalyst-commits
mailing list