browser, not in the console window from which you're running your
application, which is where logging output usually goes.
+B<Note:> You will want to disable
+L<StackTrace|Catalyst::Plugin::StackTrace> before you put your
+application into production, but it can be helpful during development.
+
=back
Note that when specifying plugins on the C<use Catalyst> line, you can
One option would be to create a separate schema file for each table in
the database, however, lets use the same L<DBIx::Class::Schema::Loader>
used earlier with C<create=dynamic> to build the static files for us.
-First, lets remove the schema file created in Part 2:
+First, lets remove the schema file created earlier:
$ rm lib/MyApp/Schema.pm
most recent version of the Catalyst Tutorial can be found at
L<http://dev.catalyst.perl.org/repos/Catalyst/trunk/Catalyst-Manual/lib/Catalyst/Manual/Tutorial/>.
-Copyright 2006, Kennedy Clark, under Creative Commons License
+Copyright 2006-2008, Kennedy Clark, under Creative Commons License
(L<http://creativecommons.org/licenses/by-nc-sa/2.5/>).