# Always remember to do all digits for the version even if they're 0
# i.e. first release of 0.XX *must* be 0.XX000. This avoids fBSD ports
# brain damage and presumably various other packaging systems too
-our $VERSION = '0.04999_04';
+our $VERSION = '0.04999_06';
__PACKAGE__->mk_classaccessor('_loader_args' => {});
__PACKAGE__->mk_classaccessors(qw/dump_to_dir _loader_invoked _loader loader_class/);
=head2 loader_class
+=over 4
+
+=item Argument: $loader_class
+
+=back
+
Set the loader class to be instantiated when L</connection> is called.
If the classname starts with "::", "DBIx::Class::Schema::Loader" is
prepended. Defaults to L<DBIx::Class::Schema/storage_type> (which must
=head2 loader_options
+=over 4
+
+=item Argument: \%loader_options
+
+=back
+
Example in Synopsis above demonstrates a few common arguments. For
detailed information on all of the arguments, most of which are
only useful in fairly complex scenarios, see the
=head2 connection
-See L<DBIx::Class::Schema> for basic usage.
+=over 4
+
+=item Arguments: @args
+
+=item Return Value: $new_schema
+
+=back
+
+See L<DBIx::Class::Schema/connection> for basic usage.
If the final argument is a hashref, and it contains the keys C<loader_options>
or C<loader_class>, those keys will be deleted, and their values value will be
=head2 clone
-See L<DBIx::Class::Schema>.
+See L<DBIx::Class::Schema/clone>.
=cut
=head2 dump_to_dir
-Argument: directory name.
+=over 4
+
+=item Argument: $directory
+
+=back
Calling this as a class method on either L<DBIx::Class::Schema::Loader>
or any derived schema class will cause all affected schemas to dump
=head2 make_schema_at
+=over 4
+
+=item Arguments: $schema_name, \%loader_options, \@connect_info
+
+=item Return Value: $schema_name
+
+=back
+
This simple function allows one to create a Loader-based schema
in-memory on the fly without any on-disk class files of any
kind. When used with the C<dump_directory> option, you can
=head2 rescan
+=over 4
+
+=item Return Value: @new_monikers
+
+=back
+
Re-scans the database for newly added tables since the initial
load, and adds them to the schema at runtime, including relationships,
etc. Does not process drops or changes.