- fixture_sets (fixture_sets)
- SEE ALSO
- COPYRIGHT & LICENSE
DBIx::Class::Migration::Script::Help::populate - Install fixtures to a database
dbic-migration populate --fixture_set core --fixture_set countries
Installs a prepared migration to either the current schema version or the target version specified via "to_version" to the database connected via the "dsn", "username" and "password" (or to a developer level sandbox as defined by the "sandbox_type").
You can't install to a database if the tables already exist. See
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").
See DBIx::Class::Migration for author information
See DBIx::Class::Migration for copyright and license information