Catalyst::Model::DBIC::Schema - DBIx::Class::Schema Model Class


Catalyst::Model::DBIC::Schema - DBIx::Class::Schema Model Class


Manual creation of a DBIx::Class::Schema and a Catalyst::Model::DBIC::Schema:

  1. Create the DBIx:Class schema in MyApp/Schema/
      package MyApp::Schema::FilmDB;
      use base qw/DBIx::Class::Schema/;
      __PACKAGE__->load_classes(qw/Actor Role/);

  2. Create some classes for the tables in the database, for example an Actor in MyApp/Schema/FilmDB/
      package MyApp::Schema::FilmDB::Actor;
      use base qw/DBIx::Class/

    and a Role in MyApp/Schema/

      package MyApp::Schema::FilmDB::Role;
      use base qw/DBIx::Class/

    Notice that the schema is in MyApp::Schema, not in MyApp::Model. This way it's usable as a standalone module and you can test/run it without Catalyst.

  3. To expose it to Catalyst as a model, you should create a DBIC Model in MyApp/Model/
      package MyApp::Model::FilmDB;
      use base qw/Catalyst::Model::DBIC::Schema/;
          schema_class => 'MyApp::Schema::FilmDB',
          connect_info => [
                            {AutoCommit => 1}

    See below for a full list of the possible config parameters.

Now you have a working Model, accessing your separate DBIC Schema. Which can be used/accessed in the normal Catalyst manner, via $c->model():

  my $actor = $c->model('FilmDB::Actor')->find(1);

You can also use it to set up DBIC authentication with Authentication::Store::DBIC in

  package MyApp;
  use Catalyst qw/... Authentication::Store::DBIC/;
  __PACKAGE__->config->{authentication}{dbic} = {
      user_class      => 'FilmDB::Actor',
      user_field      => 'name',
      password_field  => 'password'

$c->model() returns a the DBIx::Class::ResultSet manpage for the source name parameter passed. To find out more about which methods can be called on a ResultSet, or how to add your own methods to it, please see the ResultSet documentation in the the DBIx::Class manpage distribution.

Some examples are given below:

  # to access schema methods directly:
  # to access the source object, resultset, and class:
  # For resultsets, there's an even quicker shortcut:
  # is the same as $c->model('FilmDB')->resultset('Actor')
  # To get the composed schema for making new connections:
  my $newconn = $c->model('FilmDB')->composed_schema->connect(...);
  # Or the same thing via a convenience shortcut:
  my $newconn = $c->model('FilmDB')->connect(...);
  # or, if your schema works on different storage drivers:
  my $newconn = $c->model('FilmDB')->composed_schema->clone();
  # and again, a convenience shortcut
  my $newconn = $c->model('FilmDB')->clone();


This is a Catalyst Model for the DBIx::Class::Schema manpage-based Models. See the documentation for the Catalyst::Helper::Model::DBIC::Schema manpage for information on generating these Models via Helper scripts.


This is the classname of your the DBIx::Class::Schema manpage Schema. It needs to be findable in @INC, but it does not need to be inside the Catalyst::Model:: namespace. This parameter is required.

This is an arrayref of connection parameters, which are specific to your storage_type (see your storage type documentation for more details).

This is not required if schema_class already has connection information defined inside itself (which isn't highly recommended, but can be done)

For the DBIx::Class::Storage::DBI manpage, which is the only supported storage_type in the DBIx::Class manpage at the time of this writing, the parameters are your dsn, username, password, and connect options hashref.

See connect_info in the DBIx::Class::Storage::DBI manpage for a detailed explanation of the arguments supported.


  connect_info => [ 'dbi:Pg:dbname=mypgdb', 'postgres', '' ],
  connect_info => [
                      on_connect_do => [
                        'PRAGMA synchronous = OFF',
  connect_info => [
                    { AutoCommit => 0 },
                      on_connect_do => [
                        'some SQL statement',
                        'another SQL statement',

Allows the use of a different storage_type than what is set in your schema_class (which in turn defaults to ::DBI if not set in current the DBIx::Class manpage). Completely optional, and probably unnecessary for most people until other storage backends become available for the DBIx::Class manpage.


Instantiates the Model based on the above-documented ->config parameters. The only required parameter is schema_class. connect_info is required in the case that schema_class does not already have connection information defined for it.

Accessor which returns the connected schema being used by the this model. There are direct shortcuts on the model class itself for schema->resultset, schema->source, and schema->class.

Accessor which returns the composed schema, which has no connection info, which was used in constructing the schema above. Useful for creating new connections based on the same schema/model. There are direct shortcuts from the model object for composed_schema->clone and composed_schema->connect

Shortcut for ->composed_schema->clone

Shortcut for ->composed_schema->connect

Shortcut for ->schema->source

Shortcut for ->schema->class

Shortcut for ->schema->resultset

Provides an accessor for the connected schema's storage object. Used often for debugging and controlling transactions.


General Catalyst Stuff:

the Catalyst::Manual manpage, the Catalyst::Test manpage, the Catalyst::Request manpage, the Catalyst::Response manpage, the Catalyst::Helper manpage, Catalyst,

Stuff related to DBIC and this Model style:

the DBIx::Class manpage, the DBIx::Class::Schema manpage, the DBIx::Class::Schema::Loader manpage, the Catalyst::Helper::Model::DBIC::Schema manpage


Brandon L Black,


This program is free software, you can redistribute it and/or modify it under the same terms as Perl itself.

 Catalyst::Model::DBIC::Schema - DBIx::Class::Schema Model Class