% sqlite /tmp/myapp.db < myapp.sql
-Now we can create a DBIC::SchemaLoader component for this database.
+Now we can create a DBIC::Schema model for this database.
- script/myapp_create.pl model DBIC DBIC::SchemaLoader 'dbi:SQLite:/tmp/myapp.db'
+ script/myapp_create.pl model MyModel DBIC::Schema MySchema create=static 'dbi:SQLite:/tmp/myapp.db'
L<DBIx::Class::Schema::Loader> automatically loads table layouts and
-relationships. Use the stash to pass data to your templates.
+relationships, and converts them into a static schema definition C<MySchema>,
+which you can edit later.
+
+Use the stash to pass data to your templates.
We add the following to MyApp/Controller/Root.pm
sub view : Global {
my ( $self, $c, $id ) = @_;
- $c->stash->{item} = $c->model('DBIC::Foo')->find($id);
+ $c->stash->{item} = $c->model('MyModel::Foo')->find($id);
}
1;
and C<MyApp::Controller::Catalog::Order::begin> would override this in
turn.
+=over 4
+
=item * B<auto : Private>
In addition to the normal built-in actions, you have a special action
the I<most> specific class. I<This is the reverse of the order in which
the normal built-ins override each other>.
+=back
+
Here are some examples of the order in which the various built-ins
would be called:
=head1 SEE ALSO
+=over 4
+
=item * L<Catalyst::Manual::About>
=item * L<Catalyst::Manual::Tutorial>
=item * L<Catalyst>
+=back
+
=head1 SUPPORT
IRC: