1 package DBIx::Class::Schema::Loader;
5 use base qw/DBIx::Class::Schema/;
6 use base qw/Class::Data::Accessor/;
8 use UNIVERSAL::require;
10 use Data::Dump qw/ dump /;
11 use Scalar::Util qw/ weaken /;
13 # Always remember to do all digits for the version even if they're 0
14 # i.e. first release of 0.XX *must* be 0.XX000. This avoids fBSD ports
15 # brain damage and presumably various other packaging systems too
16 our $VERSION = '0.03001';
18 __PACKAGE__->mk_classaccessor('dump_to_dir');
19 __PACKAGE__->mk_classaccessor('loader');
20 __PACKAGE__->mk_classaccessor('_loader_args');
24 DBIx::Class::Schema::Loader - Dynamic definition of a DBIx::Class::Schema
29 use base qw/DBIx::Class::Schema::Loader/;
31 __PACKAGE__->loader_options(
33 constraint => '^foo.*',
37 # in seperate application code ...
41 my $schema1 = My::Schema->connect( $dsn, $user, $password, $attrs);
43 my $schema1 = "My::Schema"; $schema1->connection(as above);
47 DBIx::Class::Schema::Loader automates the definition of a
48 L<DBIx::Class::Schema> by scanning database table definitions and
49 setting up the columns and primary keys.
51 DBIx::Class::Schema::Loader currently supports DBI for MySQL,
52 Postgres, SQLite and DB2.
54 See L<DBIx::Class::Schema::Loader::DBI::Writing> for notes on writing
55 your own vendor-specific subclass for an unsupported DBD driver.
57 This module requires L<DBIx::Class> 0.06 or later, and obsoletes
58 the older L<DBIx::Class::Loader>.
60 This module is designed more to get you up and running quickly against
61 an existing database, or to be effective for simple situations, rather
62 than to be what you use in the long term for a complex database/project.
64 That being said, transitioning your code from a Schema generated by this
65 module to one that doesn't use this module should be straightforward and
66 painless (as long as you're not using any methods that are now deprecated
67 in this document), so don't shy away from it just for fears of the
68 transition down the road.
74 Example in Synopsis above demonstrates a few common arguments. For
75 detailed information on all of the arguments, most of which are
76 only useful in fairly complex scenarios, see the
77 L<DBIx::Class::Schema::Loader::Base> documentation.
79 This method is *required*, for backwards compatibility reasons. If
80 you do not wish to change any options, just call it with an empty
81 argument list during schema class initialization.
89 if(ref $_[0] eq 'HASH') {
96 my $class = ref $self || $self;
97 $args{schema} = $self;
98 $args{schema_class} = $class;
99 weaken($args{schema}) if ref $self;
101 $self->_loader_args(\%args);
102 $self->_invoke_loader if $self->storage && !$class->loader;
109 my $class = ref $self || $self;
111 $self->_loader_args->{dump_directory} ||= $self->dump_to_dir;
113 # XXX this only works for relative storage_type, like ::DBI ...
114 my $impl = "DBIx::Class::Schema::Loader" . $self->storage_type;
116 croak qq/Could not load storage_type loader "$impl": / .
117 qq/"$UNIVERSAL::require::ERROR"/;
119 # XXX in the future when we get rid of ->loader, the next two
120 # lines can be replaced by "$impl->new(%{$self->_loader_args})->load;"
121 $class->loader($impl->new(%{$self->_loader_args}));
122 $class->loader->load;
130 See L<DBIx::Class::Schema>.
135 my $self = shift->next::method(@_);
137 my $class = ref $self || $self;
138 $self->_invoke_loader if $self->_loader_args && !$class->loader;
145 See L<DBIx::Class::Schema>.
152 my $clone = $self->next::method(@_);
154 $clone->_loader_args($self->_loader_args);
155 $clone->_loader_args->{schema} = $clone;
156 weaken($clone->_loader_args->{schema});
163 Argument: directory name.
165 Calling this as a class method on either L<DBIx::Class::Schema::Loader>
166 or any derived schema class will cause all affected schemas to dump
167 manual versions of themselves to the named directory when they are
168 loaded. In order to be effective, this must be set before defining a
169 connection on this schema class or any derived object (as the loading
170 happens as soon as both a connection and loader_options are set, and
171 only once per class).
173 See L<DBIx::Class::Schema::Loader::Base/dump_directory> for more
174 details on the dumping mechanism.
176 This can also be set at module import time via the import option
177 C<dump_to_dir:/foo/bar> to L<DBIx::Class::Schema::Loader>, where
178 C</foo/bar> is the target directory.
182 # My::Schema isa DBIx::Class::Schema::Loader, and has connection info
183 # hardcoded in the class itself:
184 perl -MDBIx::Class::Schema::Loader=dump_to_dir:/foo/bar -MMy::Schema -e1
186 # Same, but no hard-coded connection, so we must provide one:
187 perl -MDBIx::Class::Schema::Loader=dump_to_dir:/foo/bar -MMy::Schema -e 'My::Schema->connection("dbi:Pg:dbname=foo", ...)'
189 # Or as a class method, as long as you get it done *before* defining a
190 # connection on this schema class or any derived object:
192 My::Schema->dump_to_dir('/foo/bar');
193 My::Schema->connection(........);
195 # Or as a class method on the DBIx::Class::Schema::Loader itself, which affects all
199 DBIx::Class::Schema::Loader->dump_to_dir('/foo/bar');
200 My::Schema->connection(.......);
201 My::OtherSchema->connection(.......);
203 # Another alternative to the above:
204 use DBIx::Class::Schema::Loader qw| dump_to_dir:/foo/bar |;
207 My::Schema->connection(.......);
208 My::OtherSchema->connection(.......);
215 foreach my $opt (@_) {
216 if($opt =~ m{^dump_to_dir:(.*)$}) {
217 $self->dump_to_dir($1)
219 elsif($opt eq 'make_schema_at') {
221 my $cpkg = (caller)[0];
222 *{"${cpkg}::make_schema_at"} = \&make_schema_at;
227 =head2 make_schema_at
229 This simple function allows one to create a Loader-based schema
230 in-memory on the fly without any on-disk class files of any
231 kind. When used with the C<dump_directory> option, you can
232 use this to generate a rought draft manual schema from a dsn
233 without the intermediate step of creating a physical Loader-based
236 This function can be exported/imported by the normal means, as
237 illustrated in these Examples:
239 # Simple example, creates as a new class 'New::Schema::Name' in
240 # memory in the running perl interpreter.
241 use DBIx::Class::Schema::Loader qw/ make_schema_at /;
244 { relationships => 1, debug => 1 },
245 [ 'dbi:Pg:dbname="foo"','postgres' ],
248 # Complex: dump loaded schema to disk, all from the commandline:
249 perl -MDBIx::Class::Schema::Loader=make_schema_at,dump_to_dir:./lib -e 'make_schema_at("New::Schema::Name", { relationships => 1 }, [ "dbi:Pg:dbname=foo","postgres" ])'
251 # Same, but inside a script, and using a different way to specify the
253 use DBIx::Class::Schema::Loader qw/ make_schema_at /;
256 { relationships => 1, debug => 1, dump_directory => './lib' },
257 [ 'dbi:Pg:dbname="foo"','postgres' ],
263 my ($target, $opts, $connect_info) = @_;
265 my $opts_dumped = dump($opts);
266 my $cinfo_dumped = dump(@$connect_info);
269 use base qw/DBIx::Class::Schema::Loader/;
270 __PACKAGE__->loader_options($opts_dumped);
271 __PACKAGE__->connection($cinfo_dumped);
277 Using the example in L<DBIx::Class::Manual::ExampleSchema> as a basis
278 replace the DB::Main with the following code:
282 use base qw/DBIx::Class::Schema::Loader/;
284 __PACKAGE__->loader_options(
288 __PACKAGE__->connection('dbi:SQLite:example.db');
292 and remove the Main directory tree (optional). Every thing else
295 =head1 DEPRECATED METHODS
297 You don't need to read anything in this section unless you're upgrading
298 code that was written against pre-0.03 versions of this module. This
299 version is intended to be backwards-compatible with pre-0.03 code, but
300 will issue warnings about your usage of deprecated features/methods.
302 =head2 load_from_connection
304 This deprecated method is now roughly an alias for L</loader_options>.
306 This method *will* dissappear in a future version.
308 For now, using this method will invoke the legacy behavior for
309 backwards compatibility, and merely emit a warning about upgrading
312 It also reverts the default inflection scheme to
313 use L<Lingua::EN::Inflect> just like pre-0.03 versions of this
316 You can force these legacy inflections with the
317 option C<legacy_default_inflections>, even after switch over
318 to the preferred L</loader_options> way of doing things.
320 See the source of this method for more details.
324 sub load_from_connection {
325 my ($self, %args) = @_;
326 warn 'load_from_connection deprecated, please [re-]read the'
327 . ' [new] DBIx::Class::Schema::Loader documentation';
329 # Support the old connect_info / dsn / etc args...
330 $args{connect_info} = [
333 delete $args{password},
334 delete $args{options},
337 $self->connection(@{delete $args{connect_info}})
338 if $args{connect_info};
340 $self->loader_options('legacy_default_inflections' => 1, %args);
345 This is an accessor in the generated Schema class for accessing
346 the L<DBIx::Class::Schema::Loader::Base> -based loader object
347 that was used during construction. See the
348 L<DBIx::Class::Schema::Loader::Base> docs for more information
349 on the available loader methods there.
351 This accessor is deprecated. Do not use it. Anything you can
352 get from C<loader>, you can get via the normal L<DBIx::Class::Schema>
353 methods, and your code will be more robust and forward-thinking
356 If you're already using C<loader> in your code, make an effort
357 to get rid of it. If you think you've found a situation where it
358 is neccesary, let me know and we'll see what we can do to remedy
361 In some future version, this accessor *will* disappear. It was
362 apparently quite a design/API mistake to ever have exposed it to
363 user-land in the first place, all things considered.
367 =head2 Multiple Database Schemas
369 Currently the loader is limited to working within a single schema
370 (using the database vendors' definition of "schema"). If you
371 have a multi-schema database with inter-schema relationships (which
372 is easy to do in Postgres or DB2 for instance), you only get to
373 automatically load the tables of one schema, and any relationships
374 to tables in other schemas will be silently ignored.
376 At some point in the future, an intelligent way around this might be
377 devised, probably by allowing the C<db_schema> option to be an
378 arrayref of schemas to load, or perhaps even offering schema
379 constraint/exclusion options just like the table ones.
381 In "normal" L<DBIx::Class::Schema> usage, manually-defined
382 source classes and relationships have no problems crossing vendor schemas.
386 Brandon Black, C<blblack@gmail.com>
388 Based on L<DBIx::Class::Loader> by Sebastian Riedel
390 Based upon the work of IKEBE Tomohiro
394 Adam Anderson, Andy Grundman, Autrijus Tang, Dan Kubb, David Naughton,
395 Randal Schwartz, Simon Flack, Matt S Trout, everyone on #dbix-class, and
396 all the others who've helped.
400 This library is free software; you can redistribute it and/or modify it under
401 the same terms as Perl itself.
405 L<DBIx::Class>, L<DBIx::Class::Manual::ExampleSchema>