Ubuntu 8.10 uses the older DBIC C<load_classes> vs. the newer
C<load_namspaces> technique. For new applications, please try to use
C<load_namespaces> since it more easily supports a very useful DBIC
-technique called "ResultSet Classes." This tutorial expects to migrate to
-C<load_namespaces> when the next release of Ubuntu comes out.
-
-If you wish to try C<load_namespaces> now, you can manually do the
-equivalent of the C<create=static> operation outside of the Catalyst
-helper:
-
- perl -MDBIx::Class::Schema::Loader=make_schema_at,dump_to_dir:./lib -e \
- 'make_schema_at("MyApp::Schema", { debug => 1, use_namespaces => 1, \
- components => ["InflateColumn::DateTime"] },["dbi:SQLite:myapp.db", "", "" ])'
-
-And then use the helper to only create the Catalyst model class:
-
- script/myapp_create.pl model DB DBIC::Schema MyApp::Schema dbi:SQLite:myapp.db
-
-B<However>, it is important to note that C<load_namespaces> will look
-for your C<Books.pm>, <Authors.pm>, etc. files in
-C<lib/MyApp/Schema/Result> (it adds the subdirection "Result" so that
-there can also be a "ResultSet" directory next to it in the
-hierarchy). Therefore, if you switch to C<load_namespaces>, you will
-need to modify the path to these "result class" files throughout the
-rest of the tutorial. Our recommendation for now would be to complete
-the tutorial using C<load_classes> and the try converting to
-C<load_namespaces> after you are done.
+technique called "ResultSet Classes." We will migrate to
+C<load_namespaces> in Part 4 (BasicCRUD) of this tutorial.
=head2 Updating the Generated DBIC Schema Files