- fixture_sets (fixture_sets)
- SEE ALSO
- COPYRIGHT & LICENSE
DBIx::Class::Migration::Script::Help::dump_named_sets - Dump specified fixture sets.
dbic-migration dump_named_sets --fixture_set core --fixture_set demo_db
For the current database version, dump data sets for the named fixtures. If the database is not versioned, we assume the version is whatever you schema class is.
This command accepts the following options. You may learn more about each option by typing
dbic-migration help OPTION. The following is a summary.
Required. The fixture configuration set names (basically these are the file names of your fixture configurations, without the '.json' part.
Adds the listed paths to @INC. Handy during development when you want to use a development schema class.
Accepts Str. Required.
This is the schema we use as the basis for creating, managing and running your deployments. This should be the full package namespace defining your subclass of DBIx::Class::Schema. For example
If the "schema_class" cannot be loaded, a hard exception will be thrown.
When using a
sandbox_class for generating developer level database sandboxes, you may wish to place the sandbox in a directory other than the default (which is under the
share directory off the project root).
Aliases: T, sb
Accepts: String (default: SqliteSandbox)
The class we use to create a developer level database sandbox.
Connection information to an already created and running instance of a database. If you don't specify this, we will assume you want a developer level sandbox ( See "sandbox_class"" in "DBIx::Class::Migration::Script).
Accepts: String to a Perl Class. Defaults to DBIx::Class::Fixtures
Lets you specify a fixture class.
Accepts: HashRef. Optional
Allows you to pass custom arguments to DBIx::Class::Fixtures.
See DBIx::Class::Migration for author information
See DBIx::Class::Migration for copyright and license information