Revision history for Perl extension Catalyst::Model::DBIC::Schema
-0.19 XXX Not yet released
+0.20 Wed May 23, 2007
- Fix for rt.cpan.org #22426
- Switch to Module::Install
+ - Assorted small pod and cleanliness fixes
+ - Some requirements bumped to the latest maint
+ releases of the same major feature release
0.18 Tue Aug 8 04:34:42 UTC 2006
- Version bump for public release, no functional change
name 'Catalyst-Model-DBIC-Schema';
all_from 'lib/Catalyst/Model/DBIC/Schema.pm';
-requires 'DBIx::Class' => '0.07000';
+requires 'DBIx::Class' => '0.07006';
requires 'Catalyst::Runtime' => '5.70';
requires 'UNIVERSAL::require' => '0.10';
requires 'Class::Data::Accessor' => '0.02';
requires 'Class::Accessor::Fast' => '0.22';
-requires 'Test::More';
+test_requires 'Test::More';
feature 'Catalyst::Helper support',
-default => 0,
'Catalyst::Devel' => '1.0',
- 'DBIx::Class::Schema::Loader' => '0.03006';
+ 'DBIx::Class::Schema::Loader' => '0.03012';
+if(-e 'MANIFEST.SKIP') {
+ system("pod2text lib/Catalyst/Model/DBIC/Schema.pm > README");
+}
+
+auto_provides;
auto_install;
WriteAll;
parameters are your dsn, username, password, and connect options
hashref.
- If you need to specify the DBIx::Class::Storage::DBI specific
- parameter "on_connect_do", or the related "sql_maker" options
- "limit_dialect", "quote_char", or "name_sep", you can place these
- options into a hashref as the final element of the "connect_info"
- arrayref. If in doubt, don't specify these options. You would know
- it if you needed them.
+ See "connect_info" in DBIx::Class::Storage::DBI for a detailed
+ explanation of the arguments supported.
Examples:
use strict;
use warnings;
+
+our $VERSION = '0.20';
+
use Carp;
use UNIVERSAL::require;
=head2 Arguments:
-C< CatalystModelName > is the short name for the Catalyst Model class
-being generated (i.e. callable with C< $c->model >
+C<CatalystModelName> is the short name for the Catalyst Model class
+being generated (i.e. callable with C<$c-E<gt>model('CatalystModelName')>).
-C< MyApp::SchemaClass > is the fully qualified classname of your Schema,
+C<MyApp::SchemaClass> is the fully qualified classname of your Schema,
which might or might not yet exist. Note that you should have a good
reason to create this under a new global namespace, otherwise use an
existing top level namespace for your schema class.
-C< create=dynamic > instructs this Helper to generate the named Schema
+C<create=dynamic> instructs this Helper to generate the named Schema
class for you, basing it on L<DBIx::Class::Schema::Loader> (which
means the table information will always be dynamically loaded at
runtime from the database).
-C< create=static > instructs this Helper to generate the named Schema
+C<create=static> instructs this Helper to generate the named Schema
class for you, using L<DBIx::Class::Schema::Loader> in "one shot"
mode to create a standard, manually-defined L<DBIx::Class::Schema>
setup, based on what the Loader sees in your database at this moment.
adapt itself to changes in your database structure. You can edit
the generated classes by hand to refine them.
-C< connect_info > arguments are the same as what
+C<connect_info> arguments are the same as what
DBIx::Class::Schema::connect expects, and are storage_type-specific.
For DBI-based storage, these arguments are the dsn, username,
password, and connect options, respectively. These are optional for
# in your app config, or [not recommended] in the schema itself).
script/myapp_create.pl model ModelName DBIC::Schema My::SchemaClass
-=head2 METHODS
+=head1 METHODS
-=head3 mk_compclass
+=head2 mk_compclass
=cut
package Catalyst::Model::DBIC::Schema;
use strict;
+use warnings;
+
+our $VERSION = '0.20';
+
use base qw/Catalyst::Model Class::Accessor::Fast Class::Data::Accessor/;
use NEXT;
use UNIVERSAL::require;
use Data::Dumper;
require DBIx::Class;
-our $VERSION = '0.19';
-
__PACKAGE__->mk_classaccessor('composed_schema');
__PACKAGE__->mk_accessors('schema');
C<storage_type> in L<DBIx::Class> at the time of this writing, the
parameters are your dsn, username, password, and connect options hashref.
-If you need to specify the L<DBIx::Class::Storage::DBI> specific parameter
-C<on_connect_do>, or the related C<sql_maker> options C<limit_dialect>,
-C<quote_char>, or C<name_sep>, you can place these options into a hashref
-as the final element of the C<connect_info> arrayref. If in doubt, don't
-specify these options. You would know it if you needed them.
+See L<DBIx::Class::Storage::DBI/connect_info> for a detailed explanation
+of the arguments supported.
Examples: